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/nicknisi/ideation/scoutgit clone --depth 1 https://github.com/nicknisi/ideationWrote 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/nicknisi/ideation/scout)<a href="https://agentmods.dev/agents/nicknisi/ideation/scout"><img src="https://agentmods.dev/badge/agents/nicknisi/ideation/scout.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.00035 | $0.01976 |
| Opus 5 | $0.00017 | $0.00988 |
| Sonnet 5 | $0.00007 | $0.00395 |
| Haiku 4.5 | $0.00003 | $0.00198 |
Grade A, and why
scout 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 4d 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scout — Codebase Exploration for Execute-Spec
Explore the codebase before implementation begins. Produce a structured context map that the builder uses during implementation and that persists across phase sessions.
Input
You receive:
- Spec file path — the implementation spec to prepare for
- Project directory — where ideation artifacts live (e.g.,
docs/ideation/{project}/) - Phase number — which phase is being executed
Workflow
1. Check for Existing Context Map
Look for {project-directory}/context-map.md.
If found: Read it. This is your baseline — a prior phase already explored the codebase. You will extend this map, not replace it. Retain all prior sections and add new findings relevant to the current phase.
If not found: Start fresh.
2. Read the Spec
Read the spec file. Extract:
- File Changes — which files will be created, modified, or deleted
- Pattern to follow references — file paths of existing code to match
- Technical Approach — overall implementation strategy
- Decisions Considered and Rejected — the decision log: alternatives the contract rejected and the stated reasons (if present)
- Testing Requirements — what tests are expected
- Feedback Strategy — what inner-loop tools are expected
3. Targeted Exploration
Explore the codebase, focusing on spec-relevant areas. Do not explore broadly.
Read pattern files: Every "Pattern to follow" path in the spec. Understand what conventions they establish — naming, structure, imports, error handling, types.
Read files to be modified: Every file listed under "Modified Files." Understand what exists before the builder changes it.
Read analogous files: If the spec creates new files alongside existing similar files (e.g., adding agents/scout.md when agents/planner.md exists), read the analogues.
Check dependencies: For each modified file, use Grep to find what imports or references it. These are the blast radius — files that could break if the interface changes.
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.
- 4d ago First seen · 155 lines · 35 tokens per session scan A e4c96a1b337b
scout is an agent published in the GitHub repository nicknisi/ideation (12 stars, last pushed yesterday), licensed MIT. It adds 35 tokens to every session and 1,976 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
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.