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 instructions/appunni-m/coverage-mcp/agents-mdgit clone --depth 1 https://github.com/appunni-m/coverage-mcpWrote 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/instructions/appunni-m/coverage-mcp/agents-md)<a href="https://agentmods.dev/instructions/appunni-m/coverage-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/appunni-m/coverage-mcp/agents-md.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.00689 | $0.00689 |
| Opus 5 | $0.00345 | $0.00345 |
| Sonnet 5 | $0.00138 | $0.00138 |
| Haiku 4.5 | $0.00069 | $0.00069 |
Grade A, and why
coverage-mcp AGENTS.md 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Coverage MCP Agent Notes
This repository owns the Rust Coverage MCP binary, REST API, MCP contract, storage behavior, dashboard, migration fixtures, and primary README. Keep these surfaces synchronized when changing behavior.
MCP contract change checklist
For changes to tool names, inputs, output shapes, descriptions, instructions, safety annotations, resources, pagination, or workflow:
- Update
src/mcp.rs. Initialization instructions must be sufficient for an agent without opening the README; tool descriptions must explain purpose, mode choices, budget/pagination behavior, errors, and the next step. - Update the service/storage implementation when validation or side effects change. Keep compact envelopes and hidden detailed fields consistent across HTTP and stdio.
- Update
docs/mcp-reference.mdwith every tool, input, return shape, error class, resource, and workflow rule. Update the README, getting-started guide, or user guide only when their shorter user journey changes. - Add the lowest-layer behavior test and one public HTTP or stdio test when a public input/output changes.
- Verify both transports. The shared dispatcher is
mcp::dispatch_json_rpc; do not fork transport-specific semantics.
Workflow ownership
Operational approval, polling, freshness, lineage, response-budget, and
reporting rules belong in the marketplace's testing:coverage-review skill
and the campaign skill that composes it. Keep this repository's copy limited to
the server contract and implementation invariants; do not duplicate workflow
instructions here. The server must still advertise a complete self-describing
workflow through initialize instructions and tools/list descriptions.
Rust verification
The required local gate is:
cargo fmt --all -- --check
DUCKDB_DOWNLOAD_LIB=1 cargo clippy --workspace --all-targets --no-default-features --locked -- -D warnings
DUCKDB_DOWNLOAD_LIB=1 cargo test --workspace --all-targets --no-default-features --locked -- --test-threads=1
DUCKDB_DOWNLOAD_LIB=1 cargo llvm-cov --lib --no-default-features --locked \
--ignore-filename-regex '/src/main\.rs$' \
--fail-under-lines 100 --fail-under-functions 100 --fail-under-regions 100 \
--fail-uncovered-lines 0 --fail-uncovered-functions 0 --fail-uncovered-regions 0 -- --test-threads=1
DUCKDB_DOWNLOAD_LIB=1 RUSTDOCFLAGS='-D warnings' cargo doc --workspace --no-default-features --no-deps --locked
cargo build --release --locked
git diff --check
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.
- 4d ago First seen · 63 lines · 689 tokens per session scan A c752e89952e3
coverage-mcp AGENTS.md is an instructions file published in the GitHub repository appunni-m/coverage-mcp (0 stars, last pushed 6d ago), licensed MIT. It adds 689 tokens to every session, about $0.0034 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-31.
Other instructions, from other repositories
turso AGENTS.md
AGENTS.md instructions for tursodatabase/turso, covering turso agent guidelines, quick reference, testing, running tests and test organization.
cli AGENTS.md
AGENTS.md instructions for googleworkspace/cli, covering agents.md, project overview, build & test, changesets and architecture.
azure-sdk-for-rust resourcemanager.instructions.md
Instructions for Azure/azure-sdk-for-rust, a project described as: This repository is for the active development of the Azure SDK for Rust. For consumers of the SDK we recommend visiting Docs.rs and looking up the docs for any of libraries in the SDK.
intelligent-terminal rust.instructions.md
Concise Rust coding conventions for this repository.
bifrost AGENTS.md
AGENTS.md instructions for bifrost-proxy/bifrost, covering bifrost 项目开发规则, 执行心法, 执行模式与完成定义, 任务模式判定 and 变更类型与验证路由(先判定,后执行).
ton-rs AGENTS.md
AGENTS.md instructions for ston-fi/ton-rs, covering ton-rs agent guide, repository, boundaries, public api and ton invariants.