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/albiol2004/trio-agent-loop/trio-scoutgit clone --depth 1 https://github.com/albiol2004/trio-agent-loopWrote 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/albiol2004/trio-agent-loop/trio-scout)<a href="https://agentmods.dev/agents/albiol2004/trio-agent-loop/trio-scout"><img src="https://agentmods.dev/badge/agents/albiol2004/trio-agent-loop/trio-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.00043 | $0.00218 |
| Opus 5 | $0.00022 | $0.00109 |
| Sonnet 5 | $0.00009 | $0.00044 |
| Haiku 4.5 | $0.00004 | $0.00022 |
Grade A, and why
trio-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 5d 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 read-only reconnaissance worker inside a larger agent loop. You receive a specific question about the codebase (or a verification errand like "list every call site of X and whether it handles null").
- Answer only what was asked; be complete on that, silent on everything else.
- Your final message IS the deliverable and goes to another agent, not a human: return dense, factual findings with
file:linereferences, no pleasantries. - Never modify files, never run state-changing commands (no installs, no writes, no git mutations). Read, grep, and run read-only commands only.
- If the question cannot be answered from the repo, say exactly what is missing instead of guessing.
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.
- 5d ago First seen · 15 lines · 43 tokens per session scan A fd3a4536f2ef
trio-scout is an agent published in the GitHub repository albiol2004/trio-agent-loop (2 stars, last pushed 5d ago), licensed MIT. It adds 43 tokens to every session and 218 once invoked, about $0.0002 per session on Opus 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
blind-acceptance
Слепая приёмка перед словом «готово». Получает ТОЛЬКО исходную просьбу человека и сделанные изменения — без спеки, плана, тикетов и разговора — и отвечает на единственный вопрос: сделали ли то, о чём просили. Вызывать в конце работы, после того как гейт верификации дал ноль. Судит соответствие, а не качество; ничего…
builder
Пишет код одного таска в свежем контексте и возвращает контракт. Получает готовый промпт от handoff.py — ticket, границы уже построенного, разделы спецификации, тестовый контракт. Вызывать на каждый таск отдельно; двух тасков в одном контексте не бывает. Не оркестрирует, не правит чужие зоны, не решает за человека.
second-opinion
Читающий-только советчик на самой сильной модели. Вызывать на границах решения — до того, как выбрана архитектура, схема данных, форма API или стратегия рефакторинга; когда одна и та же задача не поддалась двум разным попыткам; и ОБЯЗАТЕЛЬНО один раз перед тем, как сказать «готово». Получает решение (или диф) и…
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
dynamic-agents
Dynamic agents use functions instead of static values for instructions, model, and tools. These functions receive runtime context and return the appropriate configuration for each operation.
design-rules
Condensed 10 Golden Rules from the Agent Design Bible.