← ClaudeAtlas

ai-agents-meta-corelisted

Shared reference for the ai-agents-meta cluster: the eval-first + default-deny-autonomy model every spoke turns on, plus shared conventions (the agent stack, cold-start briefs, cost routing tiers) and the gate/loop/cost matrix. USE WHEN wiring an autonomous loop, granting an agent tools, setting an eval gate, or routing by model cost — the interlocking rules every meta spoke shares.
Sheshiyer/skill-clusters · ★ 0 · AI & Automation · score 69
Install: claude install-skill Sheshiyer/skill-clusters
# AI Agents Meta Core Shared model for the `ai-agents-meta` cluster. The planning, orchestration, loop, audit, and cost spokes all depend on these interlocking ideas — keep them consistent here so no spoke contradicts another. ## 1. The decision this cluster turns on: eval-first × default-deny autonomy Every spoke is an answer to one question: **how much can this agent do on its own, and how do we know it did it right?** The cluster's stance is two coupled rules: ``` Plan ──gated by──> Eval ──authorizes──> Autonomous step ──bounded by──> Tool / loop budget ``` - **Eval-first** — no step that an agent runs unattended ships without a *gate that can fail it* (a test, a review, a schema/assertion, a screenshot diff). The gate is designed *before* the step, not bolted on after. → `agentic-engineering`, `dynamic-workflow-mode`, `continuous-agent-loop` - **Default-deny autonomy** — an agent gets the **narrowest** tool set, permission, and loop budget that lets the gated step pass. Widening any of them (a new tool, a higher iteration cap, write access) is a governance change worth stating out loud. → `team-agent-orchestration`, `agentic-os` **Rule:** if you can't name the gate that fails the step, the step isn't ready to be autonomous — drop it back to a human checkpoint. ## 2. The agent stack (what the audit spokes inspect) Agent failures localize to a layer. Reason top-down before patching: | Layer (top → bottom) | Typical failure | Spoke | |---|---|---| | Prompt /