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/matteocervelli/llms/coverage-analyzernpx skills add matteocervelli/llms --skill coverage-analyzergit clone --depth 1 https://github.com/matteocervelli/llmsWhat 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.00035 | $0.03730 |
| Opus 5 | $0.00017 | $0.01865 |
| Sonnet 5 | $0.00007 | $0.00746 |
| Haiku 4.5 | $0.00003 | $0.00373 |
Grade C, and why
coverage-analyzer scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf .coverage htmlcov/ How it starts
The opening of the file, as written. The whole thing — 683 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Coverage Analyzer Skill
Purpose
This skill provides comprehensive test coverage analysis, gap identification, threshold validation, and detailed reporting to ensure code quality and adequate test coverage across the codebase.
When to Use
- Measuring test coverage for a module or project
- Identifying untested code and coverage gaps
- Validating coverage meets threshold (≥ 80%)
- Generating coverage reports for review
- Analyzing coverage trends over time
- Finding missing branch coverage
Coverage Analysis Workflow
1. Basic Coverage Measurement
Run Tests with Coverage:
# Install pytest-cov if not installed
pip install pytest-cov
# Basic coverage measurement
pytest --cov=src tests/
# Coverage with terminal report
pytest --cov=src --cov-report=term tests/
# Coverage with missing lines
pytest --cov=src --cov-report=term-missing tests/
# Coverage for specific module
pytest --cov=src.tools.feature tests/
Quick Coverage Check:
# Show percentage only
pytest --cov=src --cov-report=term tests/ | grep TOTAL
# Check if coverage meets threshold
pytest --cov=src --cov-fail-under=80 tests/
# Quiet mode with coverage
pytest --cov=src --cov-report=term -q tests/
Deliverable: Basic coverage metrics
2. Detailed Coverage Analysis
Generate Detailed Reports:
# HTML coverage report (most detailed)
pytest --cov=src --cov-report=html tests/
# Open htmlcov/index.html in browser
# XML coverage report (for CI/CD)
pytest --cov=src --cov-report=xml tests/
# JSON coverage report
pytest --cov=src --cov-report=json tests/
# Multiple report formats
pytest --cov=src \
--cov-report=html \
--cov-report=xml \
--cov-report=term-missing \
tests/
Analyze Coverage by Module:
# Show coverage for each file
pytest --cov=src --cov-report=term tests/
# Coverage with line numbers
pytest --cov=src --cov-report=term-missing tests/
# Annotated source files
pytest --cov=src --cov-report=annotate tests/
# Creates .py,cover files with coverage annotations
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 · 683 lines · 35 tokens per session scan C 56093b327011
coverage-analyzer is a skill published in the GitHub repository matteocervelli/llms (25 stars, last pushed 3mo ago), licensed MIT. It adds 35 tokens to every session and 3,730 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-01.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…