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 commands/generous-corp/pulp/coverage-diffgit clone --depth 1 https://github.com/Generous-Corp/pulpWrote 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/generous-corp/pulp/coverage-diff)<a href="https://agentmods.dev/commands/generous-corp/pulp/coverage-diff"><img src="https://agentmods.dev/badge/commands/generous-corp/pulp/coverage-diff.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.00021 | $0.00326 |
| Opus 5 | $0.00010 | $0.00163 |
| Sonnet 5 | $0.00004 | $0.00065 |
| Haiku 4.5 | $0.00002 | $0.00033 |
Grade A, and why
coverage-diff 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 yesterday.
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
Run the local diff-coverage check before pushing. Mirrors CI's Diff coverage required (75%) gate so coverage-only failures don't cost a 20-min CI roundtrip.
Threshold + filters live in tools/scripts/coverage_config.json — edit there once and CI + local stay in sync.
If $ARGUMENTS is provided, treat it as a space-separated list of test targets to build (faster path):
tools/scripts/local_diff_cover.sh $ARGUMENTS
Otherwise build everything (slow, matches CI):
tools/scripts/local_diff_cover.sh
Bypass on doc-only / workflow-only PRs:
PULP_SKIP_DIFF_COVER=1 tools/scripts/local_diff_cover.sh
If the script fails:
- Read the HTML report for the per-file uncovered-line breakdown. The script
prints its path at the end — it is written under this worktree's
build-cov/, so read the path it printed rather than assuming a shared location. - Add a test that exercises the new lines, or refactor to remove the dead branch.
- The pre-push hook enforces this check by default when relevant code changed;
PULP_DISABLE_PREPUSH_DIFF_COVER=1demotes only diff-cover to advisory.
If the script can't run because diff-cover isn't installed:
pip install --user 'diff-cover>=9'
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.
- yesterday First seen · 41 lines · 21 tokens per session scan A be402758c8a6
coverage-diff is a command published in the GitHub repository Generous-Corp/pulp (16 stars, last pushed yesterday), licensed MIT. It adds 21 tokens to every session and 326 once invoked, about $0.0001 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-09-04.
Other commands, from other repositories
ci-setup
Setup CI pipeline from scratch. Creates GitHub Actions or GitLab CI configuration with lint, test, build, and deploy stages.
ship
Mechanical pre-deploy gate — tests, build, tree state.
harness:cicd-fleet
Autonomous CI/CD-remediation orchestrator — triage the red CI/CD-run and flaky-test backlog by cause, fan out worktree-isolated subagents that run the real deflake/heal pipeline, independently verify each fix by artifact and deterministic all-OS CI, and hand back a batch of remediation PRs for one bulk human review.…
ship
Before merging or deploying, run ALL of the following checks. Every gate must pass.
test-setup
Scaffold test framework and CI pipeline.
verify
Runs the fastest possible verification for changed stacks. Returns binary PASS/FAIL with counts.