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 lukedj78/dev-flow --skill write-testsgit clone --depth 1 https://github.com/lukedj78/dev-flowWrote 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/lukedj78/dev-flow/write-tests)<a href="https://agentmods.dev/skills/lukedj78/dev-flow/write-tests"><img src="https://agentmods.dev/badge/skills/lukedj78/dev-flow/write-tests/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/lukedj78/dev-flow/write-tests"><img src="https://agentmods.dev/badge/skills/lukedj78/dev-flow/write-tests.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00176 | $0.03076 |
| Opus 5.5 | $0.00070 | $0.01230 |
| Sonnet 5.5 | $0.00035 | $0.00615 |
| Haiku 4.5 | $0.00018 | $0.00308 |
Grade A, and why
write-tests 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 3d 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
write-tests — generate tests for one file at a time
This skill writes the test file that should sit next to a piece of source code. One invocation = one source file → one test file. It does not install test infrastructure (that's module-add test), does not debug failing tests (that's superpowers:systematic-debugging), and does not run an HTTP-based QA pass (that's qa).
The unit of work is deliberately small because tests rot when they're auto-generated in bulk. A single file at a time forces the user to read what was written and accept it before moving to the next.
When this skill applies
- The user names a source file: "scrivi i test per
lib/server/clienti.ts", "test perapp/checkout/page.tsx", "e2e per /scadenze". - The orchestrator routes here from
module_added(test infrastructure exists) when the user wants per-feature coverage. - The project has a wired test stack —
meta.json#stack.testis set, ORvitest.config.ts+playwright.config.tsexist at the root.
Contract
This skill follows the dev-flow contract — see references/contracts.md. Key facts:
- Reads
<root>/.workflow/meta.json#stack.testto confirm the test framework is wired. - Reads the project's existing
vitest.setup.ts,vitest.config.ts,playwright.config.ts, and any sibling test files to learn the mocking style — does not re-prescribe patterns from scratch. - Writes a single test file alongside the source (
__tests__/<name>.test.tsfor unit,e2e/<name>.spec.tsfor e2e). - Does NOT bump
phase— tests are continuous work, not a phase transition. - Appends to
meta.json#historywith the source file path, the test path, and the test type. - Idempotent: if the test file already exists, ask the user — either regenerate, append missing cases, or abort. Never silently overwrite.
Workflow
Step 1 — Verify prerequisites
Read <project-root>/.workflow/meta.json:
stack.frameworkmust benext, ormonorepowith the test aimed atapps/web/. Onexpo-rn(or a file underapps/mobile/), stop and hand off torn-write-tests:stack.testalone does not tell the two apart —jest-expo+rntlis a valid value too — and this skill's Vitest/Playwright patterns are wrong for React Native.stack.testmust be set (e.g.,"vitest+playwright"). Ifnull, stop and tell the user: "Test infrastructure not wired. Runmodule-add testfirst, then come back."phaseshould bemodule_addedor later. If earlier, the project might not have anything testable yet — warn and ask whether to proceed.
What ships with it
7 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.
- 3d ago Changed · +1 lines db02c7b6bb7f
- 4d ago Changed · +1 lines · +11 tokens per session a0704dd4e7f3
- 11d ago Changed · +3 lines 35b8d5cf5499
- 16d ago Changed · +8 lines 8f0aa79c0724
- 1mo ago First seen · 161 lines · 165 tokens per session scan A 8d297b5afcc4
write-tests is a skill published in the GitHub repository lukedj78/dev-flow (6 stars, last pushed yesterday), licensed MIT. It adds 176 tokens to every session and 3,076 once invoked, about $0.0007 per session on Opus 5.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
ios-testing-patterns
XCTest and XCUITest execution workflows and flaky test detection patterns.
test-automation
Execute Vitest and Playwright test suites with result collection and failure analysis.
testing-strategy
Comprehensive testing skill covering unit, integration, and e2e testing with TDD. Use when writing tests, improving coverage, or setting up testing infrastructure. Keywords: test, TDD, unit test, integration, e2e, coverage, mock, jest, vitest.
senior-qa
Generates unit tests, integration tests, and E2E tests for React/Next.js applications. Scans components to create Jest + React Testing Library test stubs, analyzes Istanbul/LCOV coverage reports to surface gaps, scaffolds Playwright test files from Next.js routes, mocks API calls with MSW, creates test fixtures, and…
test-generation-patterns
Use this skill when generating tests with AI assistance. Activate when the user wants to create unit tests, integration tests, generate test cases, improve test coverage, write tests for existing code, or set up testing patterns for their project.
running-tests
Provides test execution order, failure interpretation, and verification discipline. Triggered before commits, after code changes, or when verifying quality.