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/omermaksutii/RugProofWrote 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/commands/omermaksutii/rugproof/coverage)<a href="https://agentmods.dev/commands/omermaksutii/rugproof/coverage"><img src="https://agentmods.dev/badge/commands/omermaksutii/rugproof/coverage/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/commands/omermaksutii/rugproof/coverage"><img src="https://agentmods.dev/badge/commands/omermaksutii/rugproof/coverage.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.00015 | $0.00423 |
| Opus 5.5 | $0.00006 | $0.00169 |
| Sonnet 5.5 | $0.00003 | $0.00085 |
| Haiku 4.5 | $0.00002 | $0.00042 |
Grade A, and why
coverage 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
/coverage — close test coverage gaps
Procedure
Step 1 — Run coverage
mcp__forge-runner__coverage(format=json)
Returns per-file branch / line / function coverage.
Step 2 — Identify gaps
For each file under src/:
- Lines covered < 90%? Identify which lines.
- Branches covered < 80%? Identify which branches.
Step 3 — Generate targeted tests
For each gap, generate a test that exercises the uncovered path. Lean on /test-gen infrastructure.
Common gap patterns:
- Revert branches (
requirefailure paths) — write a test that triggers the revert. - Conditional logic (
if (x > 10)) — test both arms. - Loop edge cases (empty array, single element, max bound).
Step 4 — Re-run coverage
Verify the new tests close the gaps. Iterate.
Step 5 — Output
Coverage:
Before: src/Vault.sol lines 78% / branches 71%
src/Oracle.sol lines 92% / branches 84%
After: src/Vault.sol lines 96% / branches 88% ✓
src/Oracle.sol lines 98% / branches 91% ✓
Generated:
test/generated/coverage/VaultGaps.t.sol (12 tests)
test/generated/coverage/OracleGaps.t.sol (4 tests)
Notes
- 100% line coverage is achievable. 100% branch coverage is harder; aim for 90%.
- Some lines are intentionally untested (e.g. unreachable revert in storage-init). Allow
// rugproof-skip-coverageinline. - Coverage is a minimum, not a measure of correctness. High coverage + no invariants is misleading.
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 · 56 lines · 15 tokens per session scan A f0de67ee0246
coverage is a command published in the GitHub repository omermaksutii/RugProof (10 stars, last pushed 2mo ago), licensed MIT. It adds 15 tokens to every session and 423 once invoked, about $0.0001 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-31.
Other commands, from other repositories
krait-fuzz
Run an invariant-based fuzzing campaign: Understand → Extract Invariants → Generate Foundry Tests → Run & Fix Iteratively → Report.
verify-e2e-flow
Verify that the E2E scripts for the specified chain follow the documented transaction flow.
fix-bch-e2e-p1
Fix errors in BCH E2E test (Pattern 1: P2PKH Single-sig).
fix-btc-e2e-p1
Fix errors in BTC E2E test (Pattern 1: P2PKH Single-sig).
fix-btc-e2e-p11
Fix errors in BTC E2E test (Pattern 11: P2TR Tapscript M-of-N).
fix-btc-e2e-p2
Fix errors in BTC E2E test (Pattern 2: P2PKH 2-of-3 Multisig).