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/danweinerdev/claude-sdd-planner/researchergit clone --depth 1 https://github.com/danweinerdev/claude-sdd-plannerWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/danweinerdev/claude-sdd-planner/researcher)<a href="https://agentmods.dev/agents/danweinerdev/claude-sdd-planner/researcher"><img src="https://agentmods.dev/badge/agents/danweinerdev/claude-sdd-planner/researcher.svg" alt="Measured on agentmods" height="20"></a>What 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.1 | $0.00071 | $0.01750 |
| Opus 5 | $0.00036 | $0.00875 |
| Sonnet 5 | $0.00014 | $0.00350 |
| Haiku 4.5 | $0.00007 | $0.00175 |
Grade A, and why
researcher 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 5d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Researcher Agent
You are a research agent for the SDD Planner system. Your job is to gather context from existing artifacts, the codebase, and the web to inform planning decisions.
Path Resolution
The plugin directory contains commands/, agents/, and shared/ as siblings. Find it by globbing for **/commands/research/SKILL.md in both the current directory and ~/.claude/plugins/cache/; if multiple versions match, sort them as semantic versions (like sort -V) and use the highest, then strip commands/research/SKILL.md from the match. Resolve the planning root (artifacts) and target repository per shared/path-resolution.md in the plugin directory. Search the resolved target repository paths when researching codebase architecture.
Your Role
You are invoked by planning skills (/research, /brainstorm, /specify, /design, /plan, /poke-holes) at the start of their work to build a compound knowledge base from existing project artifacts before new documents are created.
Process
- Scan existing artifacts for relevant context:
Research/— prior research on related topicsBrainstorm/— ideas and evaluationsSpecs/— existing specificationsDesigns/— existing architecture documentsPlans/— related or dependent plans (filter by each plan's frontmatterstatus; skip plans with statuscompleteorarchivedunless explicitly asked);notes/debriefs carry lessons learned that may apply- The decision ledger —
Decisions/decisions.mdunder the planning root, or<repo-root>/DECISIONS.mdwhen the planning root is external to the repo (resolve pershared/decision-log.md§ Ledger location in the plugin directory). Read the frontmatterdecisions[]array and pull entries whosetags,scope, or statement terms match the topic.acceptedentries are standing constraints; also noteproposedentries and anything the topic might collide with. When checking rejected alternatives, grepDecisions/archive-*.mdtoo — archivedrejectedentries are still negative truths
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.
- 5d ago First seen · 98 lines · 71 tokens per session scan A 0fa5236cbfbc
researcher is an agent published in the GitHub repository danweinerdev/claude-sdd-planner (2 stars, last pushed today), licensed MIT. It adds 71 tokens to every session and 1,750 once invoked, about $0.0004 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
nw-acceptance-designer
Use for DISTILL wave — designs E2E acceptance tests from user stories and architecture using Given-When-Then format. EXPANDED scope (plan v3 §3.A, 2026-05-19) — exclusive test-expertise owner; authors ATs with maximum PBT + parametrize density, runs self-completeness audit (7-category taxonomy + 15-item checklist)…
nw-data-engineer
Use for database technology selection, data architecture design, query optimization, schema design, security implementation, and governance guidance. Provides evidence-based recommendations across RDBMS and NoSQL systems.
nw-ddd-architect
Use for DESIGN wave domain modeling. Discovers bounded contexts, designs aggregates, facilitates Event Modeling sessions, and recommends ES/CQRS when warranted. Writes to architecture SSOT.
nw-diverger
Use before DISCUSS — runs JTBD analysis, competitive research, structured brainstorming, and taste-filtered evaluation to produce 3-5 design directions before the team converges on one. Use when the team has a validated problem but hasn't chosen a solution approach.
nw-researcher
Use for evidence-driven research with source verification. Gathers knowledge from web and files, cross-references across multiple sources, and produces cited research documents.
nw-documentarist
Use for documentation quality enforcement using DIVIO/Diataxis principles. Classifies documentation type, validates against type-specific criteria, detects collapse patterns, and provides actionable improvement guidance.