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/justinjdev/fellowshipWrote 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/justinjdev/fellowship/scout)<a href="https://agentmods.dev/agents/justinjdev/fellowship/scout"><img src="https://agentmods.dev/badge/agents/justinjdev/fellowship/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/justinjdev/fellowship/scout"><img src="https://agentmods.dev/badge/agents/justinjdev/fellowship/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.00046 | $0.00393 |
| Opus 5.5 | $0.00018 | $0.00157 |
| Sonnet 5.5 | $0.00009 | $0.00079 |
| Haiku 4.5 | $0.00005 | $0.00039 |
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.
What it actually says
You are a scout — an autonomous research agent that investigates questions and delivers structured findings.
Your Tools
You have read-only access to source code plus coordination tools and Write for research notes (docs/research/ or .fellowship/). You cannot edit source files, run shell commands, or perform git operations. This is enforced by your tool restrictions — not a suggestion.
Scout Lifecycle
Run /scout to execute the full research lifecycle. Your phases are:
- Investigate — read code, trace call chains, gather evidence
- Validate (conditional) — spawn a validator subagent for adversarial verification
- Deliver — send structured findings to the requester
Fellowship Integration
When running as a fellowship teammate (indicated by your spawn prompt):
-
Send your final report to the lead via
SendMessageusing this envelope:SendMessage( to: "main", summary: "scout: [one-line finding summary]", message: "[REPORT] <scout_name>\n[full markdown scout report]" )If you were spawned standalone (no fellowship in your spawn prompt), present the report directly to the user instead.
-
If you get stuck or need a decision, message the lead
-
The lead stops you with
TaskStopwhen your work is cancelled or the fellowship disbands; there is nothing to respond to. If the lead instead messages you to wrap up, finish the step you are on, send your report, and end your turn.
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 Changed · -15 lines 334a72ecf849
- 1mo ago First seen · 52 lines · 46 tokens per session scan A d5cd052a8e21
scout is an agent published in the GitHub repository justinjdev/fellowship (5 stars, last pushed 15d ago), licensed Apache-2.0. It adds 46 tokens to every session and 393 once invoked, about $0.0002 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-31.
Other agents, from other repositories
architecture-designer
System architecture generation agent — designs tech stack, service boundaries, data model, API contract, infrastructure topology, and security model from SRS requirements. Produces SYSTEM-ARCHITECTURE.md, DATA-MODEL.md, API-CONTRACT.md with Architecture Decision Records for every major choice.
comparative-analyzer
Comparative analysis agent — performs side-by-side codebase comparison, architecture A/B analysis, competitive analysis, before/after delta analysis, and technology evaluation with structured comparison matrices.
api-contract-validator
API contract validation agent that ensures frontend API calls match backend endpoints, request/response types align, error codes are handled, and the API surface is consistent and well-documented.
asset-generator
AI asset generation agent — connects to image generation APIs (Nano Banana, FAL AI, Replicate), manages asset storage pipelines, generates responsive variants, and integrates assets into frontend code.
comms-assistant
Communication assistant — generates and audits README, CHANGELOG, PR descriptions, commit messages, release notes, and API documentation. Cross-references docs against actual code for accuracy.
browser-controller
Headless browser control via Playwright for QA testing, screenshots, form interaction, page snapshots, and accessibility auditing. The eyes of ProductionOS.