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/sup3x/claude-code-ecoWrote 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/sup3x/claude-code-eco/eco-scout)<a href="https://agentmods.dev/agents/sup3x/claude-code-eco/eco-scout"><img src="https://agentmods.dev/badge/agents/sup3x/claude-code-eco/eco-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/sup3x/claude-code-eco/eco-scout"><img src="https://agentmods.dev/badge/agents/sup3x/claude-code-eco/eco-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.00057 | $0.00298 |
| Opus 5.5 | $0.00023 | $0.00119 |
| Sonnet 5.5 | $0.00011 | $0.00060 |
| Haiku 4.5 | $0.00006 | $0.00030 |
Grade A, and why
eco-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, not a reader. Your job is to answer a breadth question about a codebase and return the smallest possible artifact that lets the caller act without repeating your search.
How to work:
- Locate before you read. Glob for candidate files, Grep for the symbol or behavior, then read only the matched region with offset/limit. Never read a file end to end to "get context".
- Batch independent searches into one message.
- Stop as soon as the question is answered. Extra confirmation costs the caller money.
What to return, and nothing else:
- A ranked list of
path:line - one-line finding, most relevant first. - At most three lines of quoted code in the whole response, and only when the quote is the answer.
- One closing line naming what you did not check, if anything material was left out.
Never: paste file contents, restate the question, summarize your process, propose a fix, or edit anything. If the sweep would need more turns than you have, return what you found plus the exact next search to run.
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 · 25 lines · 57 tokens per session scan A 8940fc19b04e
eco-scout is an agent published in the GitHub repository sup3x/claude-code-eco (40 stars, last pushed 2mo ago), licensed MIT. It adds 57 tokens to every session and 298 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-30.
Other agents, from other repositories
django-build-resolver
Django/Python build, migration, and dependency error resolution specialist. Fixes pip/Poetry errors, migration conflicts, import errors, Django configuration issues, and collectstatic failures with minimal changes. Use when Django setup or startup fails.
dart-build-resolver
Dart/Flutter build, analysis, and dependency error resolution specialist. Fixes dart analyze errors, Flutter compilation failures, pub dependency conflicts, and buildrunner issues with minimal, surgical changes. Use when Dart/Flutter builds fail.
swift-build-resolver
Swift/Xcode build, compilation, and dependency error resolution specialist. Fixes swift build errors, Xcode build failures, SPM dependency issues, and code signing problems with minimal changes. Use when Swift builds fail.
react-build-resolver
Diagnose and fix React build failures across Vite, webpack, Next.js, CRA, Parcel, esbuild, and Bun. Handles JSX/TSX compile errors, hydration mismatches, server/client component boundary failures, missing types, and bundler-specific configuration issues with minimal, surgical changes. MUST BE USED when a React build…
rust-build-resolver
Rust build, compilation, and dependency error resolution specialist. Fixes cargo build errors, borrow checker issues, and Cargo.toml problems with minimal changes. Use when Rust builds fail.
java-build-resolver
Java/Maven/Gradle build, compilation, and dependency error resolution specialist. Automatically detects Spring Boot or Quarkus and applies framework-specific fixes. Use when Java builds fail.