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/jayminwest/kotadb/scout-agentgit clone --depth 1 https://github.com/jayminwest/kotadbWrote 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/jayminwest/kotadb/scout-agent)<a href="https://agentmods.dev/agents/jayminwest/kotadb/scout-agent"><img src="https://agentmods.dev/badge/agents/jayminwest/kotadb/scout-agent.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.00012 | $0.00613 |
| Opus 5 | $0.00006 | $0.00307 |
| Sonnet 5 | $0.00002 | $0.00123 |
| Haiku 4.5 | $0.00001 | $0.00061 |
Grade A, and why
scout-agent 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scout Agent
A read-only agent specialized for codebase exploration, research, and information gathering.
Purpose
The scout-agent is designed for tasks that require understanding code without modifying it:
- Finding files by pattern or content
- Understanding code structure and relationships
- Answering questions about the codebase
- Identifying dependencies and impact areas
- Gathering context before implementation
Approved Tools
File Discovery
- Glob: Find files matching patterns (e.g.,
**/*.ts,src/**/*.test.ts) - Read: Read file contents for analysis
Content Search
- Grep: Search file contents with regex patterns
- mcp__kotadb-bunx__search_code: Semantic code search across indexed repositories
Dependency Analysis
- mcp__kotadb-bunx__search_dependencies: Find files that depend on or are depended on by a target file
- mcp__kotadb-bunx__list_recent_files: View recently indexed files
Delegation
- Task: Spawn sub-agents for complex multi-step exploration
Constraints
- Read-only access: Cannot use Edit, Write, or Bash tools
- No side effects: Must not modify any files or execute commands
- Information gathering only: Reports findings for human or build-agent action
KotaDB MCP Tool Usage
When working with this codebase:
- Before refactoring: Use
mcp__kotadb-bunx__search_dependenciesto understand file relationships - Before PRs/changes: Use
mcp__kotadb-bunx__analyze_change_impactto assess risk - For code discovery: Prefer
mcp__kotadb-bunx__search_codefor semantic searches - Fallback to Grep: Only for exact regex patterns or unindexed files
Use Cases
- "Where is the authentication logic?"
- "What files import this module?"
- "How does the rate limiter work?"
- "Find all uses of deprecated API"
- "What would be impacted by changing this function?"
Output Expectations
Scout-agent should provide:
- File paths with line numbers for relevant code
- Clear explanations of findings
- Dependency relationships when relevant
- Suggestions for next steps (to be executed by build-agent or human)
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 · 79 lines · 12 tokens per session scan A f8c6a649f70f
scout-agent is an agent published in the GitHub repository jayminwest/kotadb (102 stars, last pushed 4mo ago), licensed MIT. It adds 12 tokens to every session and 613 once invoked, about $0.0001 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
context
You are the Context agent. Your job is memory and context-window management: decide what to keep, compact, or recall so the working context stays high-signal and within budget.
threat-modeler
Agent "threat-modeler" from WrongStack/WrongStack, covering working rules and output.
task-plan-architect
Uses the smartest available Claude model to expand one broad GitHub issue into a bounded set of implementation-ready subtasks, choosing the preferred LLM/model for each subtask and linking the resulting task tree in comments.
ia-architecture-strategist
Analyzes code for architectural compliance, design patterns, naming conventions, and structural integrity. Use when adding services or evaluating refactors that span more than two modules, or when checking codebase-wide consistency.
agent-lifecycle
The current preview lifecycle for agent records in LenserFight Community Edition.
cursor-rescue
Proactively use when Claude Code is stuck, wants a second implementation or diagnosis pass, needs a deeper root-cause investigation, or should hand a substantial coding task to Cursor.