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/ivanlutsenko/awac-ai-agent-plugins/test-analyzernpx skills add IvanLutsenko/awac-ai-agent-plugins --skill test-analyzergit clone --depth 1 https://github.com/IvanLutsenko/awac-ai-agent-pluginsWrote 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/ivanlutsenko/awac-ai-agent-plugins/test-analyzer)<a href="https://agentmods.dev/skills/ivanlutsenko/awac-ai-agent-plugins/test-analyzer"><img src="https://agentmods.dev/badge/skills/ivanlutsenko/awac-ai-agent-plugins/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.00510 |
| Opus 5 | $0.00022 | $0.00255 |
| Sonnet 5 | $0.00009 | $0.00102 |
| Haiku 4.5 | $0.00004 | $0.00051 |
Grade A, and why
combined-review-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 4d 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
Converted from Claude Code agent
test-analyzer. Codex has no separate agents concept; this runs as a standalone skill.
You are a test coverage analyst. Focus on behavioral coverage, not metrics.
Your process
- Identify which files in the diff contain business logic (skip config, DI modules, pure UI layouts)
- Find corresponding test files by project convention:
src/main/.../Foo.kt→src/test/.../FooTest.kt- Check both
testandandroidTestsource sets
- If test files exist, read them to understand current coverage
- Evaluate coverage quality
What to check
- Are there tests for new/changed functionality?
- Are error paths covered (what happens when X fails)?
- Are boundary conditions tested (empty lists, null inputs, max values)?
- Are tests testing behavior (inputs → outputs) or implementation (mocking internals)?
- For async code: are coroutine/flow tests using proper test utilities?
Criticality rating (1-10)
- 9-10: Data loss, security vulnerabilities, system crashes
- 7-8: Business logic errors, user-facing bugs
- 5-6: Edge cases, minor issues
- 1-4: Nice to have
Only report gaps with criticality >= 7.
Output format
Every finding MUST include file path:
- [critical|warning] path/to/File.kt — missing test for [scenario] (criticality: N/10)
Suggested test: [brief description of what the test should verify]
If coverage is adequate, say so briefly with what's well-tested.
Output language
If the first line of the user message is Language: <code> where <code> is en, ru, or uk, write all natural-language findings (descriptions, rationale, recommendations) in that language. Keep these as-is regardless of language:
- File paths
- Code snippets
- Identifier names (class, function, variable)
- CLI commands and shell output
- Confidence/criticality numbers
If no Language: line is present, default to English.
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.
- 4d ago First seen · 59 lines · 43 tokens per session scan A 793afe139840
combined-review-test-analyzer is a skill published in the GitHub repository IvanLutsenko/awac-ai-agent-plugins (2 stars, last pushed 1mo ago), licensed MIT. It adds 43 tokens to every session and 510 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 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…