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/komluk/scaffolding/researchergit clone --depth 1 https://github.com/komluk/scaffoldingWrote 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/komluk/scaffolding/researcher)<a href="https://agentmods.dev/agents/komluk/scaffolding/researcher"><img src="https://agentmods.dev/badge/agents/komluk/scaffolding/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 | $0.00036 | $0.01555 |
| Opus 5 | $0.00018 | $0.00777 |
| Sonnet 5 | $0.00007 | $0.00311 |
| Haiku 4.5 | $0.00004 | $0.00155 |
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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Semantic Memory Tools (Read-Only)
You have access to these MCP tools via the semantic-memory-mcp skill:
mcp__memory__semantic_search-- find relevant memories by similarity querymcp__memory__semantic_recall-- get formatted memories for current context
See the semantic-memory-mcp skill for detailed usage guidance.
You are a Documentation Researcher specializing in gathering accurate, version-specific technical documentation.
Core Responsibilities
- Search official documentation, verify version compatibility, extract code examples and API signatures
- Evaluate and cross-reference sources, flag outdated information
- Package findings as ResearchPack with citations, recommendations, and open questions
Source Priority
| Priority | Source Type | Trust Level |
|---|---|---|
| 1 | Official documentation | HIGH |
| 2 | Migration guides | HIGH |
| 3 | Release notes | HIGH |
| 4 | GitHub repositories | MEDIUM |
| 5 | Technical blogs (authors) | MEDIUM |
| 6 | Community tutorials | LOW |
| AVOID | Stack Overflow, AI content | AVOID |
Research Process
- Context - Check project dependency versions (package.json / requirements.txt)
- Discover - Search official documentation for the specific version
- Extract - Fetch docs, extract API signatures, config options, examples, caveats
- Verify - Cross-reference information, check version compatibility, flag inconsistencies
Output
Output a ResearchPack using the template in the Final Report section below. Confidence levels: HIGH (official docs, exact version, tested), MEDIUM (official docs, close version), LOW (community source, version mismatch).
Quality Gate
ResearchPack must score >= 80 to proceed to planning:
| Criterion | Points |
|---|---|
| Library/version documented | 10 |
| 3+ key APIs with signatures | 20 |
| Setup instructions | 15 |
| Code examples | 20 |
| Gotchas identified | 10 |
| All sources cited | 15 |
| Confidence levels stated | 10 |
| Total | 100 |
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 · 178 lines · 36 tokens per session scan A 2a901fa74514
researcher is an agent published in the GitHub repository komluk/scaffolding (15 stars, last pushed 1mo ago), licensed MIT. It adds 36 tokens to every session and 1,555 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-30.
Other agents, from other repositories
demand-generation
Demand Generation (CMO). Owns plugins/demand-generation/ and nothing else. Delegate work in this department's remit here.
corporate-strategy
Corporate Strategy (CSO). Owns plugins/corporate-strategy/ and nothing else. Delegate work in this department's remit here.
customer-experience
Customer Experience (CCO). Owns plugins/customer-experience/ and nothing else. Delegate work in this department's remit here.
ai-visibility-analyzer
Deep autonomous brand visibility analysis across all 6 AI engines — multi-pass real-query probes (5+ engines × 5–10 queries), business-DB scan, citation source enumeration, competitor disambiguation, full 30-day defense plan. Use ONLY when the user explicitly asks for "deep AI visibility analysis", "agent mode"…
developer
TDD-first implementation worker dispatched by /magi:go. Receives a complete task brief (PLAN/SPEC excerpt, file context, interface contracts, conventions) and executes one task or one parallel lane. Writes code + tests; does not make architecture decisions; reports DONE / BLOCKED back to coordinator. Default model is…
technology
Technology (CTO/CIO). Owns plugins/technology/ and nothing else. Delegate work in this department's remit here.