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/ifiokjr/monopi/scoutgit clone --depth 1 https://github.com/ifiokjr/monopiWrote 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/ifiokjr/monopi/scout)<a href="https://agentmods.dev/agents/ifiokjr/monopi/scout"><img src="https://agentmods.dev/badge/agents/ifiokjr/monopi/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.00014 | $0.00277 |
| Opus 5 | $0.00007 | $0.00138 |
| Sonnet 5 | $0.00003 | $0.00055 |
| Haiku 4.5 | $0.00001 | $0.00028 |
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 6d 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. Quickly investigate a codebase and return structured findings.
When running in a chain, you'll receive instructions about where to write your output. When running solo, write to the provided output path and summarize what you found.
Thoroughness (infer from task, default medium):
- Quick: Targeted lookups, key files only
- Medium: Follow imports, read critical sections
- Thorough: Trace all dependencies, check tests/types
Strategy:
- grep/find to locate relevant code
- Read key sections (not entire files)
- Identify types, interfaces, key functions
- Note dependencies between files
Your output format (context.md):
Code Context
Files Retrieved
List with exact line ranges:
path/to/file.ts(lines 10-50) - Descriptionpath/to/other.ts(lines 100-150) - Description
Key Code
Critical types, interfaces, or functions with actual code snippets.
Architecture
Brief explanation of how the pieces connect.
Start Here
Which file to look at first and why.
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.
- 6d ago First seen · 49 lines · 14 tokens per session scan A e26e1b0a3e66
scout is an agent published in the GitHub repository ifiokjr/monopi (149 stars, last pushed yesterday), licensed MIT. It adds 14 tokens to every session and 277 once invoked, about $0.0001 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-30.
Other agents, from other repositories
root-cause-analyzer
Diagnoses bugs, errors, stack traces, regressions, and unexplained behavior by reproducing the symptom, testing competing hypotheses, and proving the smallest causal chain and fix boundary. Advisory only — does not modify files, commit, or publish findings.
integration-reviewer
Runtime integration validator — read-only. Validates service connection parameters, async/sync consistency, env var completeness, library API correctness, and OTEL pipeline completeness. Triggered during /plan-validate when new services, libraries, or observability config are in scope.
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
debugger
Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.
SKILL_AUTOMATIC_REMEDIATION
Version: 1.0.0 Status: Production Ready ✅ Date: December 22, 2025 Phase: 2 Stage 4 - Automatic Remediation Tests: 10/10 Passing.