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/ldayton/dippy/check-coveragenpx skills add ldayton/Dippy --skill check-coveragegit clone --depth 1 https://github.com/ldayton/DippyWhat 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.00025 | $0.00417 |
| Opus 5 | $0.00013 | $0.00209 |
| Sonnet 5 | $0.00005 | $0.00083 |
| Haiku 4.5 | $0.00003 | $0.00042 |
Grade A, and why
check-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
Ensure the handler and tests for $ARGUMENTS provide comprehensive coverage.
1. Gather Documentation
Find documentation for the tool (need at least one source):
tldr:
ls ~/source/tldr/pages/*/$ARGUMENTS*.md
cat ~/source/tldr/pages/*/$ARGUMENTS.md
Local CLI:
$ARGUMENTS --help
man $ARGUMENTS
Stop if neither source exists.
2. Explore Subcommands
For tools with subcommands, recursively explore:
$ARGUMENTS <subcommand> --help
$ARGUMENTS help <subcommand>
Build a mental model of:
- All subcommands and their actions
- Which operations are read-only (safe) vs mutate state (unsafe)
- Global flags that affect parsing
- Edge cases
3. Review Existing Tests
Read tests/cli/test_$ARGUMENTS.py and check for:
- Coverage of all subcommands
- Both safe and unsafe variants of each action
- Global flag handling
- Edge cases from the docs
4. Add Missing Tests
Add aspirational test cases for anything missing. Follow existing format:
TESTS = [
# --- Subcommand group ---
("$ARGUMENTS <subcommand> <safe-action>", True),
("$ARGUMENTS <subcommand> <unsafe-action>", False),
]
5. Iterate Until Tests Pass
just test
For each failure, determine if the test expectation is correct:
- If yes, update
src/dippy/cli/$ARGUMENTS.py - If no, fix the test
6. Verify
just check MUST pass before you're done.
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 · 74 lines · 25 tokens per session scan A 058968e99ef4
check-coverage is a skill published in the GitHub repository ldayton/Dippy (243 stars, last pushed 2mo ago), licensed MIT. It adds 25 tokens to every session and 417 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-08-30.
Other skills, from other repositories
rust-unit-tests
Write, improve, and run Rust unit tests in the warp Rust codebase.
tui-testing
Write and run unit tests for Warp TUI (crates/warptui) elements/screens by rendering to text lines. Use for TUI test work.
build-and-test
Build the Wassette workspace and run its test suite with the just recipes — debug and release builds, example and test components, and the combined unit plus documentation tests. Use when compiling Wassette, building example components, or running and debugging tests.
add-assertion
Add new assertion function with comprehensive tests following TDD.
speeding-up-laravel-tests
Use when Laravel/Pest test suites are slow, CI duration is growing, individual tests take seconds, or the user asks to speed up, optimize, or profile tests. Covers factories, fakes, config caching, XDebug/pcov, BCRYPTROUNDS, LazilyRefreshDatabase, and stray HTTP requests.
django-verification
Verification loop for Django projects: migrations, linting, tests with coverage, security scans, and deployment readiness checks before release or PR.