Claude With Skills is a progressive course that teaches developers to create reusable, portable Agent Skills for Claude Code, from basic SKILL.md files to advanced automation and plugin packaging. It is intended for developers who want repeatable instructions and workflows instead of repeatedly pasting the same guidance. The catalogue contains the course's skills, agents, and instruction.
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 skills add davila7/claude-with-skills --skill test-coverage-checkgit clone --depth 1 https://github.com/davila7/claude-with-skillsWrote 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/davila7/claude-with-skills/test-coverage-check)<a href="https://agentmods.dev/skills/davila7/claude-with-skills/test-coverage-check"><img src="https://agentmods.dev/badge/skills/davila7/claude-with-skills/test-coverage-check/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/davila7/claude-with-skills/test-coverage-check"><img src="https://agentmods.dev/badge/skills/davila7/claude-with-skills/test-coverage-check.svg" alt="Reviewed on agentmods" width="80" 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.00034 | $0.00643 |
| Opus 5 | $0.00017 | $0.00321 |
| Sonnet 5 | $0.00007 | $0.00129 |
| Haiku 4.5 | $0.00003 | $0.00064 |
Grade A, and why
test-coverage-check 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 12d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Check whether changed source files have test coverage.
Changed source files
!git diff --name-only HEAD~1 2>/dev/null || git diff --name-only origin/main...HEAD 2>/dev/null || echo "none"
Filter the list above to source files only. Exclude:
- Files already in test directories (
test/,spec/,__tests__/,tests/) - Files with
.test.,.spec.in the name - Non-source files:
.md,.json,.yaml,.yml,.lock,.txt,.env,.gitignore - Configuration files:
*.config.ts,*.config.js,vite.config.*,jest.config.*
If the output was "none" or after filtering there are no source files, output: COVERAGE FINDINGS: none — no changed source files detected
Check each source file
For each changed source file, derive candidate test file paths using these conventions:
Given source file src/utils/parser.ts, check for:
src/utils/parser.test.tssrc/utils/parser.spec.tssrc/utils/__tests__/parser.tssrc/utils/__tests__/parser.test.tstests/utils/parser.test.tstests/utils/parser.spec.tstest/utils/parser.test.tstest/utils/parser.spec.ts
Apply the same pattern for .py, .js, .jsx, .tsx, .go, .rb files, substituting the appropriate test file extension:
- Python:
_test.pyortest_<name>.py - JavaScript/TypeScript:
.test.js,.spec.js,.test.ts,.spec.ts - Go:
_test.goin the same directory - Ruby:
_spec.rbinspec/
Use Glob to check whether any of the candidate paths exist.
If a test file is found, use Grep to check whether it imports or requires the source file, or references the source file's name. If no import is found, mark as "test file exists but may not cover new changes".
Output format
Output exactly:
COVERAGE FINDINGS:
- <source-file> — no test file found
- <source-file> — test file exists but may not cover new changes
Examples:
COVERAGE FINDINGS:
- src/auth/loginHandler.ts — no test file found
- src/utils/formatDate.ts — test file exists but may not cover new changes
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.
- 12d ago First seen · 68 lines · 34 tokens per session scan A cb11e084246b
test-coverage-check is a skill published in the GitHub repository davila7/claude-with-skills (12 stars, last pushed 3mo ago), licensed MIT. It adds 34 tokens to every session and 643 once invoked, about $0.0002 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
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
neuron-evaluation-engineer
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.