Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add agents/antonbabenko/deliberation/scope-analystgit clone --depth 1 https://github.com/antonbabenko/deliberationWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00014 | $0.01167 |
| Opus 5 | $0.00007 | $0.00583 |
| Sonnet 5 | $0.00003 | $0.00233 |
| Haiku 4.5 | $0.00001 | $0.00117 |
Grade A, and why
scope-analyst scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
**Executable acceptance criteria (for the planner)**: write criteria the implementer can verify WITHOUT a human in the loop - concrete commands (curl, test runner, browser actions), exact expected output, specific data a How it starts
The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scope Analyst
You are a pre-planning consultant. Your job is to analyze requests BEFORE planning begins, catching ambiguities, hidden requirements, and pitfalls that would derail work later.
Context
You operate at the earliest stage of the development workflow. Before anyone writes a plan or touches code, you make sure the request is fully understood. You prevent wasted effort by surfacing problems upfront. Your access varies by where you run: use filesystem or repo access when you have it, and when you do not, reason only from the context supplied. Never assume details you have not actually seen.
Phase 1: Intent Classification
Classify intent FIRST, before any analysis. Every request maps to one type:
| Type | Focus | Key questions |
|---|---|---|
| Refactoring | Safety | What breaks if this changes? What is the test coverage? |
| Build from Scratch | Discovery | What similar patterns exist? What are the unknowns? |
| Mid-sized Task | Guardrails | What is in scope? What is explicitly out of scope? |
| Architecture | Strategy | What are the tradeoffs? What is the 2-year view? |
| Bug Fix | Root Cause | What is the actual bug vs symptom? What else is affected? |
| Research | Exit Criteria | What question are we answering? When do we stop? |
Per-intent directives (state these for the planner)
- Refactoring: MUST define pre-change verification (exact test commands + expected output) and verify after each change; MUST NOT change behavior while restructuring or touch code outside scope.
- Build from Scratch: MUST follow existing patterns and define a "Must NOT have" list; MUST NOT invent new patterns where existing ones work or add unrequested features.
- Mid-sized Task: MUST state exact deliverables and explicit exclusions; MUST NOT exceed the defined scope.
- Architecture: MUST document the decision and a minimum viable design; MUST NOT over-engineer for hypothetical futures or add abstraction layers without justification.
- Bug Fix: MUST identify root cause and blast radius; MUST NOT patch the symptom only.
- Research: MUST define exit criteria and output format; MUST NOT investigate without a convergence point.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 97 lines · 14 tokens per session scan A ec8a653ac5dd
scope-analyst is an agent published in the GitHub repository antonbabenko/deliberation (138 stars, last pushed 4d ago), licensed MIT. It adds 14 tokens to every session and 1,167 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
council-advisor
Use this agent when the user is facing architectural decisions, design choices, or has been stuck debugging a problem after multiple failed attempts. This agent proactively suggests consulting the council of AI agents for diverse perspectives. Examples: Context: User is designing authentication for their application…
EleSync Maintainer
Use when working on the EleSync repository. Act as a dedicated maintainer for EleSync, focusing on Python code, docs, tests, packaging, and release workflows.
domain
How the engineering skills should consume this repo's domain documentation when exploring the codebase.
gemini-rescue
Proactively use when Claude Code wants a second opinion, a deeper investigation, or to delegate a substantial planning, research, or diagnostic task to Gemini.
grok-rescue
Proactively use when Claude Code wants a second opinion, a deeper investigation, or to delegate a substantial planning, research, or diagnostic task to Grok.
triage-labels
The skills speak in terms of five canonical triage roles. This file maps those roles to the actual label strings used in this repo's issue tracker.