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 skills add fabioc-aloha/Alex_Skill_Mall --skill test-quality-analysisgit clone --depth 1 https://github.com/fabioc-aloha/Alex_Skill_MallWrote 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/fabioc-aloha/alex_skill_mall/test-quality-analysis)<a href="https://agentmods.dev/skills/fabioc-aloha/alex_skill_mall/test-quality-analysis"><img src="https://agentmods.dev/badge/skills/fabioc-aloha/alex_skill_mall/test-quality-analysis/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/skills/fabioc-aloha/alex_skill_mall/test-quality-analysis"><img src="https://agentmods.dev/badge/skills/fabioc-aloha/alex_skill_mall/test-quality-analysis.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.00077 | $0.02106 |
| Opus 5 | $0.00039 | $0.01053 |
| Sonnet 5 | $0.00015 | $0.00421 |
| Haiku 4.5 | $0.00008 | $0.00211 |
Grade A, and why
test-quality-analysis 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 6d 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 — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Quality Analysis
Detect tests that exist solely for coverage metrics, identify test smells, and score test value.
MANDATORY TELEMETRY: FIRST action → invoke
ai-starter-pack-signalwithskill_name: "test-quality-analysis"only, save returnedrun_id. On ANY exit → invoke again with samerun_id+outcome. On cancel →outcome: "partial". Non-blocking — skip silently on failure.
When to Use
- Auditing test suite quality before a release
- Suspecting tests inflate coverage without catching bugs
- User asks "are these tests any good" or "find useless tests"
What This Skill Is NOT
- Not
refactor: That improves production code. This evaluates test code.
Detection Heuristics
Detect the project's test framework by scanning test files for import/require statements and config files, then apply these patterns:
Critical (Score 1-2)
| Pattern | Why It's Bad |
|---|---|
| No assertions — test calls methods but never verifies outcomes | Exercises code without proving it works |
| Trivial assertions — asserts on constants or always-true conditions | Always passes regardless of behavior |
| Exception swallowing — catches all errors silently | Hides failures; test can never fail |
| Self-referential — asserts input equals output when transformation is identity | Tests nothing meaningful |
Warning (Score 2-3)
| Pattern | Why It's Concerning |
|---|---|
| Over-mocking — every dependency mocked; no real code executes | Tests the mock setup, not behavior |
| Coverage touching — calls methods systematically without verifying behavior | Covers lines without testing logic |
| Weak verification — checks type/shape only, not content | Misses value-level bugs |
| Missing negative path — only happy path tested | Won't catch error handling bugs |
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.
- 6d ago First seen · 207 lines · 77 tokens per session scan A 24010eeead81
test-quality-analysis is a skill published in the GitHub repository fabioc-aloha/Alex_Skill_Mall (4 stars, last pushed 3d ago), licensed MIT. It adds 77 tokens to every session and 2,106 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
flutter-bloc-state-management
Implement BLoC/Cubit state, events, transitions, and async concurrency in Flutter. Use for BLoC/Cubit feature logic, debounced/cancellable events, state rendering, or bloc tests—not generic widget-only work.
code-qualities-assessment
Assess code maintainability through 5 foundational qualities (cohesion, coupling, encapsulation, testability, non-redundancy) with quantifiable scoring rubrics. Works at method/class/module levels across multiple languages. Produces markdown reports with remediation guidance. Use when you ask to "assess…
unit-test
A Go testing workflow for writing unit tests: small tests that check individual functions or components. It supports table-driven cases, where many inputs and expected results are organised in one test, and subtests.
fuzzing-test
A Go testing guide for generating fuzz tests, which repeatedly try varied inputs to find crashes and unexpected behavior. It first checks whether the code is suitable for fuzzing.
test-component
Write React Testing Library tests for an existing component, following the project's RTL conventions (prefer role/label queries, mock at network boundary, no act()). Invoke when the user asks to test, add tests for, or cover a component.
adept-writing-tests
How to write tests in the adept Go codebase — table-driven tests with testify, golden fixtures under testdata/, the cmd/adept e2e harness, temp-dir/HOME isolation, and coverage gates. Apply when adding or changing Go tests here. (matches: /test.go).