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 skills add Jamkris/everything-gemini-code --skill ecc-tools-cost-auditgit clone --depth 1 https://github.com/Jamkris/everything-gemini-codeWrote 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/jamkris/everything-gemini-code/ecc-tools-cost-audit)<a href="https://agentmods.dev/skills/jamkris/everything-gemini-code/ecc-tools-cost-audit"><img src="https://agentmods.dev/badge/skills/jamkris/everything-gemini-code/ecc-tools-cost-audit/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/skills/jamkris/everything-gemini-code/ecc-tools-cost-audit"><img src="https://agentmods.dev/badge/skills/jamkris/everything-gemini-code/ecc-tools-cost-audit.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.00045 | $0.01417 |
| Opus 5 | $0.00023 | $0.00709 |
| Sonnet 5 | $0.00009 | $0.00283 |
| Haiku 4.5 | $0.00005 | $0.00142 |
Grade A, and why
ecc-tools-cost-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 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.
This is a copy
95% identical to ecc-tools-cost-audit — 27 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ECC Tools Cost Audit
Use this skill when the user suspects the ECC Tools GitHub App is burning cost, over-creating PRs, bypassing usage limits, or routing free users into premium analysis paths.
This is a focused operator workflow for the sibling ECC-Tools repo. It is not a generic billing skill and it is not a repo-wide code review pass.
Skill Stack
Pull these ECC-native skills into the workflow when relevant:
autonomous-loopsfor bounded multi-step audits that cross webhooks, queues, billing, and retriesagentic-engineeringfor tracing the request path into discrete, provable unitscustomer-billing-opswhen repo behavior and customer-impact math must be separated cleanlysearch-firstbefore inventing helpers or re-implementing repo-local utilitiessecurity-reviewwhen auth, usage gates, entitlements, or secrets are touchedverification-loopfor proving rerun safety and exact post-fix statetdd-workflowwhen the fix needs regression coverage in the worker, router, or billing paths
When To Use
- user says ECC Tools burn rate, PR recursion, over-created PRs, usage-limit bypass, or premium-model leakage
- the task is in the sibling
ECC-Toolsrepo and depends on webhook handlers, queue workers, usage reservation, PR creation logic, or paid-gate enforcement - a customer report says the app created too many PRs, billed incorrectly, or analyzed code without producing a usable result
Scope Guardrails
- work in the sibling
ECC-Toolsrepo, not ineverything-gemini-code - start read-only unless the user clearly asked for a fix
- do not mutate unrelated billing, checkout, or UI flows while tracing analysis burn
- treat app-generated branches and app-generated PRs as red-flag recursion paths until proved otherwise
- separate three things explicitly:
- repo-side burn root cause
- customer-facing billing impact
- product or entitlement gaps that need backlog follow-up
Workflow
1. Freeze repo scope
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 · 161 lines · 45 tokens per session scan A a7cc664016ee
ecc-tools-cost-audit is a skill published in the GitHub repository Jamkris/everything-gemini-code (88 stars, last pushed 3mo ago), licensed MIT. It adds 45 tokens to every session and 1,417 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to ecc-tools-cost-audit, differing in 27 lines, and is treated as a copy.
Other skills, from other repositories
debugging
MUST USE for any real runtime debugging across ANY language or binary — crashes, silent failures, wrong responses, stuck processes, memory leaks, async misbehavior, unexplained timing, reverse engineering. Runs a hypothesis-driven loop: form ≥3 hypotheses, investigate in parallel, after 2 failed rounds spawn Oracles…
report-bug
Create a high-signal bug issue or PR in the repo that owns the defect. Use this whenever the user asks to report, file, open, or triage a LazyAntigravity plugin, bundled component, skill, hook, MCP, installer, or packaging bug, especially when they need source-backed root cause, reproduction steps, fix guidance, and…
debug-assistant
Systematic debugging assistant that helps identify and fix bugs through structured analysis, hypothesis testing, and root cause identification. Use when facing errors, unexpected behavior, or mysterious bugs.
quick-fix
Apply a minimal, targeted fix to a specific bug or issue. Focused on speed and precision - locate the problem, make the smallest correct change, and verify. Not a planning workflow; use for small fixes, patches, and hotfixes.
lcx-report-bug
Alias for report-bug. Create a high-signal bug issue or PR in the repo that owns the defect.
incident-response-oncall
Group skill: Incident response/on-call — triage, diagnosis, tracing, logs, fix, verification, postmortem, and alerting.