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/ivanlutsenko/awac-ai-agent-plugins/test-analyzergit clone --depth 1 https://github.com/IvanLutsenko/awac-ai-agent-pluginsWhat 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.00100 | $0.00575 |
| Opus 5 | $0.00050 | $0.00287 |
| Sonnet 5 | $0.00020 | $0.00115 |
| Haiku 4.5 | $0.00010 | $0.00057 |
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 2d 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
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.
- 2d ago First seen · 58 lines · 100 tokens per session scan A 0741fa189c81
test-analyzer is an agent published in the GitHub repository IvanLutsenko/awac-ai-agent-plugins (2 stars, last pushed 1mo ago), licensed MIT. It adds 100 tokens to every session and 575 once invoked, about $0.0005 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.