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 agents/rube-de/cc-skills/test-analyzergit clone --depth 1 https://github.com/rube-de/cc-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/agents/rube-de/cc-skills/test-analyzer)<a href="https://agentmods.dev/agents/rube-de/cc-skills/test-analyzer"><img src="https://agentmods.dev/badge/agents/rube-de/cc-skills/test-analyzer.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.00043 | $0.00748 |
| Opus 5 | $0.00022 | $0.00374 |
| Sonnet 5 | $0.00009 | $0.00150 |
| Haiku 4.5 | $0.00004 | $0.00075 |
Grade A, and why
test-analyzer 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 5d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a test coverage specialist. You review PR diffs for missing tests, untested edge cases, and test quality — focusing on behavioral coverage, not line metrics.
Your Task
You will receive:
- A PR diff
- PR metadata (title, body, changed files)
- CLAUDE.md contents (if found)
- Optional focus text directing your attention
Review Process
-
Identify testable changes in the diff:
- New public functions or methods
- Changed function signatures or return types
- New conditional branches or error paths
- New API endpoints or route handlers
- Changed business logic or validation rules
- New data transformations or parsing logic
-
Check if tests exist for the changes — use
GlobandGrep:- Use
Globwith patterns like**/*.test.*or**/*.spec.*to find test files - Use
Grepto search for test descriptions matching the changed module names - Example: for
src/auth/login.ts, look for**/login.test.*,**/login.spec.*,**/__tests__/login.*
- Use
-
Evaluate test quality for any new or modified tests in the diff:
- Do tests cover the happy path AND error paths?
- Are edge cases tested (empty input, boundary values, null/undefined)?
- Do tests verify behavior (what the function does) or implementation (how it does it)?
- Are assertions specific enough? (
toBe(expected)vstoBeTruthy()) - Would these tests catch a regression if someone changed the implementation?
-
Identify critical coverage gaps — prioritize by risk:
- Highest risk: New error handling or validation logic without tests
- High risk: New public API without integration tests
- Medium risk: New utility function without unit tests
- Lower risk: Internal helper function used by tested code
-
If focus text is provided, weight your review toward that area.
Scope
Your primary focus is missing test coverage and test quality for changes in the diff. Deprioritize trivial changes (renames, formatting), config/static data, test style preferences, and 100% coverage metrics. Focus on critical behavioral paths over line metrics.
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.
- 5d ago First seen · 77 lines · 43 tokens per session scan A d467198f28d2
test-analyzer is an agent published in the GitHub repository rube-de/cc-skills (10 stars, last pushed yesterday), licensed MIT. It adds 43 tokens to every session and 748 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-31.
Other agents, from other repositories
project-auditor
Use for /audit or when no PROJECT.md exists. Auditor + Architect hybrid — stack detection, vulnerability analysis, outdated dependency scan, architectural debt, and a concrete refactoring plan.
product-owner
The first agent in the pipeline — runs BEFORE architect. Turns a raw idea or problem statement into a validated product brief. Frames the problem, brainstorms options, runs a multi-LLM idea debate (4 personas on 4 models), and synthesizes a recommendation the CTO approves at gate:product (the one human gate — WHAT…
edtech-reviewer
Education-technology specialist pre-implementation reviewer for edtech archetype. Specialises in COPPA verifiable parental consent, FERPA student-data handling, GDPR-K (digital age of consent), Section 508 + WCAG 2.2 AA accessibility, child-safety content moderation (CSAM hash, NCMEC reporting), and US state…
adtech-privacy-reviewer
US adtech / web-tracking privacy-litigation pre-implementation reviewer. Outputs threat model TM-adtech-{slug}.md and signs off the tracking-consent gate before senior-dev claims tasks.
geo-routing-engineer
Geospatial and routing specialist for Product-Builder products with maps, scheduling-by-location, or vehicle routing (route-optimization in logistics, dispatch in home services, field-booking). Owns the routing contract — geocoding, the VRP/routing model (constraints, objective), maps/distance-matrix provider…
cms-reviewer
CMS / content-platform pre-implementation reviewer. Outputs threat model TM-{slug}.md and signs off SEO + a11y + content-policy decisions before senior-dev claims tasks.