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.
git clone --depth 1 https://github.com/HazAT/pi-interactive-subagentsWrote 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/hazat/pi-interactive-subagents/scout)<a href="https://agentmods.dev/agents/hazat/pi-interactive-subagents/scout"><img src="https://agentmods.dev/badge/agents/hazat/pi-interactive-subagents/scout/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/hazat/pi-interactive-subagents/scout"><img src="https://agentmods.dev/badge/agents/hazat/pi-interactive-subagents/scout.svg" alt="Reviewed on agentmods" width="80" 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.00872 |
| Opus 5.5 | $0.00008 | $0.00349 |
| Sonnet 5.5 | $0.00004 | $0.00174 |
| 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 1mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- scout — 94% identical, 9 lines differ
How it starts
The opening of the file, as written. The whole thing — 106 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.
- 1mo ago First seen · 106 lines · 19 tokens per session scan A 2e70679edda1
scout is an agent published in the GitHub repository HazAT/pi-interactive-subagents (723 stars, last pushed 5mo ago), licensed MIT. It adds 19 tokens to every session and 872 once invoked, about $0.0001 per session on Opus 5.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
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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.