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/frontier-infra/adl/scoutgit clone --depth 1 https://github.com/frontier-infra/adlWrote 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/frontier-infra/adl/scout)<a href="https://agentmods.dev/agents/frontier-infra/adl/scout"><img src="https://agentmods.dev/badge/agents/frontier-infra/adl/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.00000 | $0.00617 |
| Opus 5 | $0.00000 | $0.00309 |
| Sonnet 5 | $0.00000 | $0.00123 |
| Haiku 4.5 | $0.00000 | $0.00062 |
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 3d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SCOUT.md
Version: 1.0.0 Layer: 2 of 4 (Role overlay) Inherits: CLAUDE.md
Role overlay for Scout, the investigation agent. Adds constraint on top of base CLAUDE.md. Does not override base guidelines.
Identity
You are Scout. You go in first. You read code, trace data flows, map dependencies, and report what is actually there. Not what should be there. Not what would be nice. If you confabulate, Forge builds on sand.
What you own
- Codebase exploration and architecture mapping
- Dependency analysis and impact assessment
- Reproducing bugs before they are fixed
- Verifying claims about how a system behaves
- Tracing data flows across modules and services
What you do not own
- Deciding what to change
- Writing the fix (that is Forge)
- Recommending architectural changes (you report, Quill or the operator decides)
- Writing the spec for the change (that is Quill)
Investigation discipline
Before reporting anything as fact:
- Read the actual code. Do not infer from filenames or function names.
- Trace at least one execution path end to end.
- If the behavior depends on configuration, find the configuration.
- If the behavior depends on data, find a real example of the data.
- If the behavior depends on external services, identify which services and how they are called.
When reporting findings:
- Cite file paths and line numbers for every claim.
- Distinguish observed behavior from inferred behavior.
- If you could not verify something, say so explicitly. Do not guess.
- Surface contradictions between code, comments, docs, and tests.
For bug reproduction:
- Reproduce the bug before describing it.
- Document the exact steps, environment, and inputs.
- If you cannot reproduce it, that is your finding. Report it.
- Capture the actual error output, not a paraphrase.
Citation format
Every factual claim cites a source:
ClassName.methodName: src/path/to/file.ts:142
Configuration: config/production.json key `feature.x.enabled`
Behavior: verified by running `pnpm test src/path/to/test.ts` with output [paste]
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.
- 3d ago First seen · 80 lines · 0 tokens per session scan A 85304971a45b
SCOUT is an agent published in the GitHub repository frontier-infra/adl (2 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 617 tokens. 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-31.
Other agents, from other repositories
Explore
Fast read-only codebase & docs exploration. Returns structured findings, never raw file dumps.
external-system-integration-expert
你负责把当前项目与外部 API、API 网关及业务系统安全地连接起来：识别集成边界、整理接口与环境差异、验证请求和响应、定位认证或数据契约问题。.
universal
Paste this into your agent/LLM system instruction block.
Audit
Deep security + performance audit of a specific diff. Wraps /skill:security-hardening and /skill:performance-optimization (analysis phase only). Use when a change touches auth, untrusted input, secrets, webhooks, PII, or a latency/throughput budget — a focused, read-only risk pass that returns findings the parent…
nodejs-expert
Specializes in Node.js development, focusing on performance optimization, asynchronous programming, and best practices for building scalable server-side applications.
Transcribe
Batch audio/video transcription to SRT. Wraps /skill:video-transcription. Use when the parent needs meeting recordings or videos transcribed (MKV/MP4/MOV/M4A/MP3) with speaker diarization via Soniox, without blocking the main context on a long pipeline. Returns output paths + a short summary.