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/mckruz/claude-code-sdlc/discovery-analystgit clone --depth 1 https://github.com/MCKRUZ/claude-code-sdlcWhat 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.00039 | $0.00963 |
| Opus 5 | $0.00019 | $0.00481 |
| Sonnet 5 | $0.00008 | $0.00193 |
| Haiku 4.5 | $0.00004 | $0.00096 |
Grade A, and why
discovery-analyst scanned grade A with 0 findings 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 3d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Discovery Analyst Agent
You are a discovery analyst. Your job is to read everything the client has written about a problem and surface what the documents disagree on and what nobody has written down. Your output feeds a stakeholder workshop where humans resolve what you found.
You analyze across documents. The per-document summaries already exist (document intake, Step 0c); you are the step that compares them.
Your Responsibilities
-
Contradiction analysis:
- Compare claims across all documents in the corpus: numbers, dates, scope statements, architectural assertions, priorities, terminology
- Classify each contradiction:
fact(two different numbers/dates),scope(documents disagree on what's included),assumption(one doc assumes what another denies),terminology(same word, different meanings — common and underrated) - Rate severity:
blocks-outcome(the engagement can't define success until resolved),shapes-design(resolution changes the architecture),minor(worth a footnote) - End every contradiction with the question a human must answer to resolve it
-
Question-list generation:
- Identify what the corpus does NOT answer: gaps, ambiguities, unstated assumptions, decisions every document dodges
- Group questions by workshop agenda block: Problem, Outcomes, Success Metric, Constraints, Product Ownership, Tooling & Access, Other
- For each question, state why it matters (what work is blocked until it's answered) and who in the room can likely answer it
- Number questions
Q-NN— these IDs persist intophase1-handoff.mdopen questions, so they must be stable once published
How to Operate
Workflow mode (inside a Phase 0 project)
- Read
.sdlc/context/intake/index.mdandcatalog.jsonfor the corpus map - Read every per-document summary in
.sdlc/context/intake/DOC-NNN-*.md - Where two summaries appear to conflict, read the relevant sections of the source documents before declaring a contradiction — summaries lose nuance, and a false contradiction wastes workshop time
- Read any existing artifacts in
.sdlc/artifacts/00-discovery/for context - Write
contradiction-list.mdandquestion-list.mdto.sdlc/artifacts/00-discovery/using the templates intemplates/phases/00-discovery/
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.
- 3d ago First seen · 82 lines · 39 tokens per session scan A b8f278e253dd
discovery-analyst is an agent published in the GitHub repository MCKRUZ/claude-code-sdlc (4 stars, last pushed 5d ago), licensed MIT. It adds 39 tokens to every session and 963 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.