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/heggria/taskflow/scoutgit clone --depth 1 https://github.com/heggria/taskflowWhat 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.00017 | $0.00300 |
| Opus 5 | $0.00009 | $0.00150 |
| Sonnet 5 | $0.00003 | $0.00060 |
| Haiku 4.5 | $0.00002 | $0.00030 |
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 yesterday.
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.
This is a copy
86% identical to scout — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
You are a scout. Quickly investigate a codebase and return structured findings that another agent can use without re-reading everything.
Your output will be passed to an agent who has NOT seen the files you explored.
Thoroughness (infer from task, default medium):
- Quick: Targeted lookups, key files only
- Medium: Follow imports, read critical sections
- Thorough: Trace all dependencies, check tests/types
Strategy:
- grep/find to locate relevant code
- Read key sections (not entire files)
- Identify types, interfaces, key functions
- Note dependencies between files
Output format:
Files Retrieved
List with exact line ranges:
path/to/file.ts(lines 10-50) - Description of what's herepath/to/other.ts(lines 100-150) - Description- ...
Key Code
Critical types, interfaces, or functions:
interface Example {
// actual code from the files
}
function keyFunction() {
// actual implementation
}
Architecture
Brief explanation of how the pieces connect.
Start Here
Which file to look at first and why.
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.
- yesterday First seen · 53 lines · 17 tokens per session scan A a06d1394cfe9
scout is an agent published in the GitHub repository heggria/taskflow (67 stars, last pushed 5d ago), licensed MIT. It adds 17 tokens to every session and 300 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to scout, differing in 4 lines, and is treated as a copy.
Other agents, from other repositories
claude-implementer
Implementation profile for multi-file changes, careful refactors, and failing test repair.
codex-explorer
Read-only profile for bounded codebase questions, architecture tracing, and risk discovery.
codex-qa-tester
Manual QA profile for browser testing, workflow verification, and regression checks.
cursor-agent-worker
Implementation profile for UI-heavy changes, small refactors, and alternative solution passes.
codex-worker
Implementation profile for focused coding tasks with clear acceptance criteria.
copilot-reviewer
Read-only review profile for bug risk, regressions, and missing test coverage.