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 skills/sup3x/claude-code-eco/eco-auditnpx skills add sup3x/claude-code-eco --skill eco-auditgit 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/skills/sup3x/claude-code-eco/eco-audit)<a href="https://agentmods.dev/skills/sup3x/claude-code-eco/eco-audit"><img src="https://agentmods.dev/badge/skills/sup3x/claude-code-eco/eco-audit.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.00091 | $0.00387 |
| Opus 5 | $0.00046 | $0.00193 |
| Sonnet 5 | $0.00018 | $0.00077 |
| Haiku 4.5 | $0.00009 | $0.00039 |
Grade A, and why
eco-audit 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
Eco audit - read-only configuration audit
Run this once, from the user's project directory:
node "${CLAUDE_PLUGIN_ROOT}/scripts/audit.mjs" $ARGUMENTS
Then:
- The script's table and settings diff are already on the user's screen as the command's output. Do not reprint them - repeating output the user can already see is exactly the waste this plugin exists to remove. Never re-summarise, re-sort or re-word the rows either: the numbers and the "est" labels are the product, and a paraphrase of them is a worse product.
- Add at most 3 lines of your own: which finding to fix first, and why.
- Never apply the diff here. Applying it is
/eco setup, which shows the diff and waits for the user to confirm. Say so and stop. - If
${CLAUDE_PLUGIN_ROOT}did not expand (the path still contains that literal text), this is a personal or project install rather than a plugin: runaudit.mjsfrom this skill's own directory - the installer stages it there - and if it is missing,scripts/audit.mjsin the claude-code-eco checkout.
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 · 21 lines · 91 tokens per session scan A 9c62473425ab
eco-audit is a skill published in the GitHub repository sup3x/claude-code-eco (33 stars, last pushed 19d ago), licensed MIT. It adds 91 tokens to every session and 387 once invoked, about $0.0005 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 skills, from other repositories
lynkr
Universal LLM gateway with intelligent routing, Graphify code intelligence, Distill compression, routing telemetry, Code Mode, and 12+ provider support. 60-80% cost reduction for Claude Code, Cursor, and Codex.
uncommonroute-release
Use when publishing UncommonRoute. A release is only complete after all required steps are done: version sync, validation, GitHub push/tag/release, PyPI publish, and npm publish.
model-router
Use when route AI model requests to the optimal provider based on task, cost, latency, and capability requirements. Manage multi-provider LLM deployments. Use when working with model router.
elicit
Form-driven Socratic discovery — batch independent decision dimensions into one multi-select-capable form instead of N button-turns. Triggers on: scope this, discovery form, ask me everything at once, multi-select question.
roundtable
Convene the multi-LLM round table — Claude, Antigravity, and Codex deliberate a question; the user chairs promotion. Triggers on: roundtable, round table, convene the table, ask the table, what do the other models think, deliberate.
spec
Spec Ladders — goal-driven spec development: brainstorm, plan, review, and execute a gated task ladder with recorded approvals. Triggers on: spec, spec ladders, brainstorm and build, plan and execute, idea to code, build from scratch.