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/dachivadachkoria/claude-code-starter-kit/test-coveragegit clone --depth 1 https://github.com/dachivadachkoria/claude-code-starter-kitWrote 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/dachivadachkoria/claude-code-starter-kit/test-coverage)<a href="https://agentmods.dev/commands/dachivadachkoria/claude-code-starter-kit/test-coverage"><img src="https://agentmods.dev/badge/commands/dachivadachkoria/claude-code-starter-kit/test-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.00013 | $0.00594 |
| Opus 5 | $0.00006 | $0.00297 |
| Sonnet 5 | $0.00003 | $0.00119 |
| Haiku 4.5 | $0.00001 | $0.00059 |
Grade A, and why
test-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.
How it starts
The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Coverage Analysis & Improvement
Analyze and improve test coverage for: $ARGUMENTS
Execution Flow
Step 1: Run Coverage Analysis
Python:
pytest --cov=src --cov-report=term-missing --cov-report=html tests/
JavaScript/TypeScript:
npm test -- --coverage --coverageReporters=text
Go:
go test -coverprofile=coverage.out ./...
go tool cover -func=coverage.out
Step 2: Parse Coverage Report
Identify:
- Files with < 80% coverage
- Specific uncovered lines/functions
- Critical paths missing tests (error handlers, edge cases)
Step 3: Prioritize by Risk
High Priority (test first):
- Public API endpoints
- Authentication/authorization logic
- Data validation functions
- Payment/transaction handlers
- Error handling paths
Medium Priority:
- Business logic in services
- Data transformation utilities
- Integration points
Low Priority:
- Simple getters/setters
- Configuration loading
- Logging statements
Step 4: Generate Missing Tests
For each uncovered section:
- Understand what the code does
- Determine why it might be untested (hard to test? edge case?)
- Create appropriate test with proper mocking
- Verify the test actually covers the target lines
Step 5: Report
📊 Coverage Report
══════════════════════════════════════
Before: 65% → After: 84% (+19%)
Files Improved:
✅ src/auth.py: 45% → 92%
✅ src/api/users.py: 70% → 88%
⚠️ src/legacy.py: 30% → 45% (needs manual review)
New Tests Created:
- tests/test_auth.py (8 tests)
- tests/test_users.py (5 tests)
Remaining Gaps:
- src/legacy.py:45-67 (complex branching)
- src/utils.py:12-15 (dead code?)
══════════════════════════════════════
Coverage Targets
| Category | Target | Minimum |
|---|---|---|
| Overall | 80% | 70% |
| Critical paths | 95% | 90% |
| New code | 90% | 80% |
| Utilities | 70% | 60% |
Options
/test-coverage - Full analysis and improvement
/test-coverage --report - Report only, no changes
/test-coverage src/auth.py - Focus on specific file
/test-coverage --critical - Only critical paths
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 · 101 lines · 13 tokens per session scan A d6644e25a356
test-coverage is a command published in the GitHub repository dachivadachkoria/claude-code-starter-kit (4 stars, last pushed 5mo ago), licensed MIT. It adds 13 tokens to every session and 594 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-31.
Other commands, from other repositories
sdlc-cycle
이슈/기획서 기준 SDLC 한 사이클(이슈→개발→테스트→검증→PR/MR)을 사람 개입 없이 자동 실행.
knowledge-graph
AGENTS.md 생태계(rules·memory·agents·skills·commands·workflows)의 연결 구조를 1장의 대시보드로 뽑는다. 온보딩·문서 정합성 점검용.
fix-issue
이슈 #$ARGUMENTS 를 처리한다(이슈 우선 워크플로).
README
반복 작업을 /이름 으로 호출. 파일명 = 커맨드 이름(fix-issue.md → /fix-issue). frontmatter name/argument-hint, 본문에 프롬프트. $ARGUMENTS 로 인자 수신.
sonar
SonarQube 정적분석 실행 및 결과 조회. 코드 품질·보안 핫스팟·커버리지 확인 시 사용.
tailtest-hunt
Run an adversarial pass on $ARGUMENTS -- explicitly try to break the source code.