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/klarlabs-studio/coverctl/agents-mdgit clone --depth 1 https://github.com/klarlabs-studio/coverctlWrote 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/klarlabs-studio/coverctl/agents-md)<a href="https://agentmods.dev/instructions/klarlabs-studio/coverctl/agents-md"><img src="https://agentmods.dev/badge/instructions/klarlabs-studio/coverctl/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 | $0.00680 | $0.00680 |
| Opus 5 | $0.00340 | $0.00340 |
| Sonnet 5 | $0.00136 | $0.00136 |
| Haiku 4.5 | $0.00068 | $0.00068 |
Grade A, and why
coverctl 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 3d 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 — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
cmd/coverctl/hosts the CLI entry point and wires infrastructure to application services.internal/domain/,internal/application/,internal/infrastructure/follow DDD: domain models contain rules, application orchestrates use cases, infrastructure provides adapters (config, Go tooling, reporting, coverprofile parsing).schemas/defines the.coverctl.yamlschema; relocate docs and fixtures near the packages they describe.- Keep generated folders (proto, mocks) tracked via the
excludelist and review them withcoverctl ignorebefore running policies.
Build, Test, and Development Commands
go test ./...runs the full suite.go test -covermode=atomic -coverpkg=./cmd/... -coverpkg=./internal/... -coverprofile=.cover/coverage.out ./...mirrors thecoverctl checkinstrumentation.go run ./cmd/coverctl checkenforces each domain's minimum from.coverctl.yaml(default 80%; some packages set explicit floors — see that file); repeat it after changing code or tests.go run ./cmd/coverctl initlaunches the Bubble Tea wizard before writing.coverctl.yaml; pass--no-interactivefor automation.go run ./cmd/coverctl ignorelists theexcludepatterns contributors already documented.relicta release --yes(GitHub Action) builds the CLI artifact and publishes releases; see.relicta.yamlfor details.
Coding Style & Naming Conventions
- Format with
gofmt, keep imports grouped, and prefer short, lowercase package names that mirror directories. - Name domain concepts clearly (
PolicyEvaluator,CoverageReport); use table-driven tests for branching logic. - Keep CLI flags in
kebab-case(e.g.,--output json) and document them in README plus.coverctl.yaml. - Inject infrastructure implementations via constructors so DDD boundaries stay intact.
Testing Guidelines
- Follow TDD: extend or add tests before production code changes. Consult
docs/tdd.mdfor examples. - Use Go’s
testingpackage; keep fixtures undertestdata/and name files*_test.go. - Meet each domain's
minin.coverctl.yaml(default 80% when unset). Rungo run ./cmd/coverctl checkuntil every slice passes.
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.
- 3d ago First seen · 37 lines · 680 tokens per session scan A e797294431c5
coverctl AGENTS.md is an instructions file published in the GitHub repository klarlabs-studio/coverctl (1 stars, last pushed 6d ago), licensed MIT. It adds 680 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
mirage CLAUDE.md
Claude Code instructions for strukto-ai/mirage, covering claude.md, repo layout, typescript packages, python/typescript parity and module layout.
mcp-steroid CLAUDE.md
Claude Code instructions for jonnyzzz/mcp-steroid, covering claude.md, agents.md, design philosophy, recursive context lookup (do this before sub-folder work), sub-folder guides and must do.
akm AGENTS.md
AGENTS.md instructions for itlackey/akm, covering akm repo notes, workflow, architecture, tests and test-isolation harness.
anywidget-mcp AGENTS.md
Instructions for peter-gy/anywidget-mcp, covering anywidget-mcp, commands, architecture, dependency rule and state invariant.
autovault CLAUDE.md
Instructions for autoworks-ai/autovault, covering claude.md, project, common commands, architecture and request flow.
wrench AGENTS.md
Instructions for hraness/wrench, a project described as: Open-source CLI and TypeScript SDK for precise web capabilities for AI agents: page capture, verified media archives, encrypted reads, and typed provider operations.