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/tmj-90/gaffer/run-coveragenpx skills add tmj-90/gaffer --skill run-coveragegit clone --depth 1 https://github.com/tmj-90/gafferWrote 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/tmj-90/gaffer/run-coverage)<a href="https://agentmods.dev/skills/tmj-90/gaffer/run-coverage"><img src="https://agentmods.dev/badge/skills/tmj-90/gaffer/run-coverage.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.00057 | $0.00377 |
| Opus 5 | $0.00028 | $0.00188 |
| Sonnet 5 | $0.00011 | $0.00075 |
| Haiku 4.5 | $0.00006 | $0.00038 |
Grade A, and why
run-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 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.
What it actually says
Measure coverage
Run the repo's coverage tool, read the real number, and evidence the result or delta. Do not chase a number with hollow tests.
Steps
- Find the coverage command from the context packet (e.g.
pnpm test --coverage,pytest --cov,go test -cover ./...,mvn jacoco:report). If silent, detect the configured tool from the manifest. - Run it and capture the exact command plus the overall percentage and, where the ticket names a unit, that file's/module's coverage.
- Compare against the threshold in the ticket/AC. If it falls short, add or extend
tests for the genuinely uncovered branches (use the
add-unit-testskill) — cover real behaviour, not lines for their own sake. - Re-run to capture the new figure. Note the before→after delta if the ticket asks for an improvement.
- Evidence: the command, the percentage (and delta). Then use the
record-evidenceskill to recordcoverage_reportagainst the AC and submit for review.
Rules
- Report the true figure from a run in this session — never estimate coverage.
- Don't write assertion-free tests just to lift the number.
- Match the repo's coverage tooling and existing thresholds.
- Run on a branch (the
create-branchskill), never a protected branch.
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 · 34 lines · 57 tokens per session scan A afc572605fe5
run-coverage is a skill published in the GitHub repository tmj-90/gaffer (2 stars, last pushed 9d ago), licensed Apache-2.0. It adds 57 tokens to every session and 377 once invoked, about $0.0003 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 skills, from other repositories
mobile-developer
Expert knowledge in mobile app development for iOS, Android, and cross-platform solutions.
skill-creator
Create or update AnkaLoop skills. Use when designing, structuring, or packaging skills with scripts, references, and assets. This skill should be used when users want to create a new skill (or update an existing skill) that extends AnkaLoop's capabilities with specialized knowledge, workflows, or tool integrations.
ai-engineer
Expert knowledge in AI/ML development, model deployment, and MLOps practices.
gh-ci-analyzer
使用 gh CLI 分析 GitHub Actions CI 日志，提供结构化的故障诊断和报告.
security-best-practices
Security best practices and vulnerability prevention guidelines.
react-developer
Expert knowledge in React development, hooks, state management, and modern React patterns.