Borrowing it
Nothing to install: this file belongs to enuno/unifi-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/enuno/unifi-mcp-server/main/.claude/commands/unifi-mcp-test-coverage.mdgit clone --depth 1 https://github.com/enuno/unifi-mcp-serverWrote 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/enuno/unifi-mcp-server/unifi-mcp-test-coverage)<a href="https://agentmods.dev/commands/enuno/unifi-mcp-server/unifi-mcp-test-coverage"><img src="https://agentmods.dev/badge/commands/enuno/unifi-mcp-server/unifi-mcp-test-coverage/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/commands/enuno/unifi-mcp-server/unifi-mcp-test-coverage"><img src="https://agentmods.dev/badge/commands/enuno/unifi-mcp-server/unifi-mcp-test-coverage.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.00014 | $0.00720 |
| Opus 5 | $0.00007 | $0.00360 |
| Sonnet 5 | $0.00003 | $0.00144 |
| Haiku 4.5 | $0.00001 | $0.00072 |
Grade A, and why
unifi-mcp-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 11d 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
Analyze test coverage for the UniFi MCP Server and identify areas needing improvement.
This command runs comprehensive coverage analysis and provides actionable recommendations to reach the 80% coverage target.
Steps to execute:
-
Run full test suite with detailed coverage:
pytest --cov=src --cov-report=term-missing --cov-report=html --cov-report=json -v -
Analyze coverage by module:
- Parse coverage.json to extract per-file coverage percentages
- Identify modules below 80% threshold
- Prioritize based on TESTING_PLAN.md priorities
-
Generate coverage gap analysis:
- List files with coverage < 80%
- Show missing lines for each file
- Calculate how many tests needed to reach 80%
-
Read TESTING_PLAN.md to understand priorities:
- Phase 1 (Critical): API client, config, webhooks
- Phase 2 (High): Tool modules by usage frequency
- Phase 3 (Medium): Utility modules
- Phase 4 (Low): Edge cases and error scenarios
-
Provide actionable recommendations:
- Which module to focus on next
- Specific functions/lines that need tests
- Suggested test scenarios to add
- Estimated effort (number of tests needed)
-
Compare with previous coverage:
- Show coverage trend (if available)
- Highlight improvements or regressions
Report back with:
- Current overall coverage percentage
- Coverage by category:
- API client modules
- Tool modules (by category)
- Model modules
- Utility modules
- Webhook modules
- Top 5 files needing the most coverage
- Recommended next steps based on TESTING_PLAN.md
- Estimated tests needed to reach 80%
Example output:
Current Coverage: 34.10%
Target: 80%
Gap: 45.90%
Coverage by Category:
✓ Models: 86.62% (above target)
✗ API Client: 45.23% (needs +34.77%)
✗ Tools: 38.54% (needs +41.46%)
✗ Webhooks: 12.00% (needs +68.00%)
Top Priority Files (from TESTING_PLAN.md Phase 1):
1. src/api/client.py - 45.23% (55 missing lines)
- Need tests for: rate limiting, error handling, retry logic
2. src/config/settings.py - 60.00% (20 missing lines)
- Need tests for: environment variable loading, validation
3. src/webhooks/receiver.py - 12.00% (88 missing lines)
- Need tests for: webhook validation, signature checking
Next Action: Focus on src/api/client.py
Estimated effort: 8-10 test cases
Expected coverage gain: +11.13%
Integration with TESTING_PLAN.md:
- Reference Phase priorities
- Track completion of milestones
- Suggest updates to the plan based on findings
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.
- 11d ago First seen · 97 lines · 14 tokens per session scan A 24c4e4cb8801
unifi-mcp-test-coverage is a command published in the GitHub repository enuno/unifi-mcp-server (250 stars, last pushed 4d ago), licensed Apache-2.0. It adds 14 tokens to every session and 720 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 commands, from other repositories
prototype
You are building a proof-of-concept for the current Grainulator sprint. Read CLAUDE.md for sprint context and claims.json for existing research claims.
verify
Run repository verification using the verification-loop skill.
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
test-coverage
Analyze test coverage and identify the highest-value gaps to fill.
tdd
A command that follows test-driven development (TDD), a method where you write tests before the code they check. It moves through writing a failing test, adding the smallest implementation, and then improving the code.
check-dev
Type-check a Z specification with fuzz.