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-strategygit 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-strategy)<a href="https://agentmods.dev/skills/onedro1d/dark-factory/test-strategy"><img src="https://agentmods.dev/badge/skills/onedro1d/dark-factory/test-strategy/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-strategy"><img src="https://agentmods.dev/badge/skills/onedro1d/dark-factory/test-strategy.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.00075 | $0.00693 |
| Opus 5 | $0.00037 | $0.00347 |
| Sonnet 5 | $0.00015 | $0.00139 |
| Haiku 4.5 | $0.00007 | $0.00069 |
Grade A, and why
test-strategy 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 8d 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Strategy + Scaffolding
Goal: protect against regressions cheaply. Test pure logic and cross-service contracts — that's where silent bugs live (record detection, object-store-key drift, data-class split, type coercion). Skip trivial getters.
Test-first (RED → GREEN → REFACTOR)
Write the test before the production code, not after — the bug/feature's
test should exist and fail (RED) first, then the implementer makes it pass
(GREEN), then refactor under green. The test list is derived from the
Design Spec's ACCEPTANCE criteria (one criterion → one named test), not
invented at validation time. The implementer may not weaken a RED test to pass;
a wrong test goes back to feature-architect. (Validation that lands after code
is test-after — a weaker guard. See .claude/context/AGENT-CONTRACTS.md.)
What to test (priority)
- The exact bug being fixed — a test that fails before the fix, passes after.
- Cross-service contracts — drift = silent wedge (object-store key shape, record fields, routing keys).
- Security/segregation — restricted vs non-restricted data routing, fail-safe defaults.
- Edge cases — empty/missing, wrong type, boundary (padding, blank + coerced value). Avoid tests needing live queue/DB/object-store (those are integration — keep a separate fixture for them).
Scaffolding conventions
Mirror the repo's existing test layout and pinned tooling versions. Common stacks:
- .NET → a
<Service>.Testsproject referencing the service.csproj(xUnit). To testprivatehelpers, widen tointernal(neverpublic) + add<InternalsVisibleTo>to the service csproj. Run:dotnet test <proj>. - Go → in-package
<file>_test.go, table-driven. If valuable logic is inlined inmain(), extract a named pure func first, then test it. Run:cd <service> && go test ./.... - Python →
test_<module>.pynext to the code or undertests/. Run:pytest.
Run before reporting — green is the bar
Run the repo's test command (e.g. dotnet test, go test ./..., pytest) and mirror an existing passing suite for structure.
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.
- 8d ago First seen · 45 lines · 75 tokens per session scan A a4c0936eaa35
test-strategy is a skill published in the GitHub repository OneDro1d/dark-factory (0 stars, last pushed today), licensed Apache-2.0. It adds 75 tokens to every session and 693 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-01.
Other skills, from other repositories
engram-testing-coverage
TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.
iterative-development
TDD iteration loops using Claude Code Stop hooks - runs tests after each response, feeds failures back automatically.
python
Python development with ruff, mypy, pytest - TDD and type safety.
nw-fp-clojure
Clojure language-specific patterns, data-first modeling, REPL-driven development, and spec.
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
mobiai-mobile-tdd
You MUST use this before writing any implementation code for a mobile feature, bug fix, refactor, or behavior change. Tests come before implementation — no exceptions.