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 OneDro1d/dark-factory --skill test-quality-gatekeepergit clone --depth 1 https://github.com/OneDro1d/dark-factoryWrote 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/onedro1d/dark-factory/test-quality-gatekeeper)<a href="https://agentmods.dev/skills/onedro1d/dark-factory/test-quality-gatekeeper"><img src="https://agentmods.dev/badge/skills/onedro1d/dark-factory/test-quality-gatekeeper/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/onedro1d/dark-factory/test-quality-gatekeeper"><img src="https://agentmods.dev/badge/skills/onedro1d/dark-factory/test-quality-gatekeeper.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.00069 | $0.01590 |
| Opus 5 | $0.00034 | $0.00795 |
| Sonnet 5 | $0.00014 | $0.00318 |
| Haiku 4.5 | $0.00007 | $0.00159 |
Grade A, and why
test-quality-gatekeeper 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 9d 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 — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Quality Gatekeeper
Assess whether tests actually protect the system from regressions. Focus on real protection, not just coverage metrics.
Core Principle
:warning: High coverage ≠ High protection. A test suite with 90% coverage can still miss critical bugs if it only tests happy paths.
When to Use
- Reviewing test coverage for a feature
- Evaluating test quality before release
- Identifying gaps in regression protection
- Assessing contract test coverage between services
- Reviewing smart contract test completeness
- Identifying flaky or unreliable tests
Review Workflow
On EVERY invocation, execute these steps:
Step 1: Map Critical Paths
Identify what MUST work for the system to be valuable:
Critical Paths:
├── Authentication flow (login, logout, session)
├── Core business logic (payments, trading, data processing)
├── Data integrity (writes, updates, deletes)
├── External integrations (APIs, webhooks, events)
└── Error handling (failures, retries, recovery)
Step 2: Inventory Existing Tests
# Find test files
find . -name "*.test.ts" -o -name "*.spec.ts" -o -name "*_test.go" | head -50
# Count tests by type
grep -r "describe\|it\|test(" --include="*.test.ts" | wc -l
# Find test commands
grep -E "test|jest|vitest|pytest|go test" package.json Makefile 2>/dev/null
Categorize tests:
| Type | Count | Coverage |
|---|---|---|
| Unit tests | [count] | [what they cover] |
| Integration tests | [count] | [what they cover] |
| E2E tests | [count] | [what they cover] |
| Contract tests | [count] | [what they cover] |
Step 3: Analyze Test Quality
For each critical path, ask:
| Question | Yes/No | Evidence |
|---|---|---|
| Is the happy path tested? | ||
| Are failure cases tested? | ||
| Are edge cases tested? | ||
| Are boundary conditions tested? | ||
| Is error handling tested? | ||
| Are race conditions tested? |
Step 4: Execute Checklist
See CHECKLIST.md for the complete test quality checklist.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 223 lines · 69 tokens per session scan A 2c3d6c6c9196
test-quality-gatekeeper is a skill published in the GitHub repository OneDro1d/dark-factory (0 stars, last pushed today), licensed Apache-2.0. It adds 69 tokens to every session and 1,590 once invoked, about $0.0003 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-01.
Other skills, from other repositories
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
neuron-evaluation-engineer
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.