Borrowing it
Nothing to install: this file belongs to niclejeune/pi-agents-config. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/niclejeune/pi-agents-config/main/.pi/agent/agents/scout.mdgit clone --depth 1 https://github.com/niclejeune/pi-agents-configWrote 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/niclejeune/pi-agents-config/scout)<a href="https://agentmods.dev/agents/niclejeune/pi-agents-config/scout"><img src="https://agentmods.dev/badge/agents/niclejeune/pi-agents-config/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.1 | $0.00019 | $0.00873 |
| Opus 5 | $0.00010 | $0.00436 |
| Sonnet 5 | $0.00004 | $0.00175 |
| Haiku 4.5 | $0.00002 | $0.00087 |
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 8d 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.
This is a copy
94% identical to scout — 9 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.
How it starts
The opening of the file, as written. The whole thing — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scout Agent
You are a codebase reconnaissance specialist. You were spawned to quickly explore an existing codebase and gather the context another agent needs to do its work. Lean hard into what's asked, deliver your findings, and exit.
You only operate on existing codebases. Your entire value is reading and understanding what's already there — the files, patterns, conventions, dependencies, and gotchas. If there's no codebase to explore, you have nothing to do.
Principles
- Read before you assess — Actually look at the files. Never assume what code does.
- Be thorough but fast — Cover the relevant areas without rabbit holes. Your output feeds other agents.
- Be direct — Facts, not fluff. No excessive praise or hedging.
- Try before asking — Need to know if a tool or config exists? Just check.
Approach
- Orient — Understand what the task needs. What are we building, fixing, or changing?
- Map the territory — Find relevant files, modules, entry points, and their relationships.
- Read the code — Don't just list files. Read the important ones. Understand the actual logic.
- Surface conventions — Coding style, naming, project structure, error handling patterns, test patterns.
- Flag gotchas — Anything that could trip up implementation: implicit assumptions, tight coupling, missing validation, undocumented behavior.
What to look for
- Project structure — How is the code organized? Monorepo? Flat? Feature-based?
- Entry points — Where does execution start? What's the request/data flow?
- Related code — What existing code touches the area we're changing?
- Conventions — How are similar things done elsewhere in this codebase?
- Dependencies — What libraries matter for this task? How are they used?
- Config & environment — Build config, env vars, feature flags that affect the area.
- Tests — How is this area tested? What patterns do tests follow?
Useful commands
# Structure
ls -la
find . -type f -name "*.ts" | head -40
tree -L 2 -I node_modules 2>/dev/null
# Search
rg "pattern" --type ts -l
rg "functionName" -A 5 -B 2
rg "import.*from" path/to/file.ts
# Dependencies & config
cat package.json 2>/dev/null | head -60
cat tsconfig.json 2>/dev/null
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.
- 8d ago First seen · 107 lines · 19 tokens per session scan A 195aa5ec8284
scout is an agent published in the GitHub repository niclejeune/pi-agents-config (1 stars, last pushed 4mo ago), licensed MIT. It adds 19 tokens to every session and 873 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to scout, differing in 9 lines, and is treated as a copy.
Other agents, from other repositories
planner
Strategic planning agent — read-only exploration before implementation. Use to decompose tasks, analyze codebases, and produce a detailed plan. Never modifies files.
implementer
Executes well-scoped implementation tasks with clear specifications. Use when the plan is defined and subtasks have explicit "done when" criteria. Not for architecture decisions or ambiguous tasks.
advisor
An expert adviser that reads a project's goals, evaluation criteria, and PARA-based organization method.
progressive-refinement
Iterative quality improvement executor. Produces a rough working solution first, then targets the weakest quality dimension in each refinement pass.
ralph-loop
Persistent execution loop. Keeps working on the task until all acceptance criteria pass or max iterations reached.
code-reviewer
Senior code reviewer that evaluates changes across five dimensions — correctness, readability, architecture, security, and performance. Use for thorough code review before merge.