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 skills/ai-driven-dev/framework/testnpx skills add ai-driven-dev/framework --skill testgit clone --depth 1 https://github.com/ai-driven-dev/frameworkWhat 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.00079 | $0.00723 |
| Opus 5 | $0.00039 | $0.00362 |
| Sonnet 5 | $0.00016 | $0.00145 |
| Haiku 4.5 | $0.00008 | $0.00072 |
Grade A, and why
test 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.
How it starts
The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test
Writes tests at the correct tier of the project's test pyramid: unit for domain and use-case logic, integration for adapter behavior and real-filesystem contracts, E2E for full CLI journeys. Bug fixes always start with a failing test that reproduces the exact reported scenario before any production code is touched.
Available actions
| # | Action | Role | Input |
|---|---|---|---|
| 01 | pick-tier |
Choose unit, integration, or e2e based on what is under test | target file or behavior |
| 02 | name-behaviorally |
Draft behavior-sentence test names | list of scenarios to cover |
| 03 | write |
Write the test file following tier conventions | tier + names from 01-02 |
| 04 | empirical-repro |
Produce an empirical reproduction transcript for user-reported bugs | bug report |
| 05 | smoke |
Run real CLI binary in /tmp, verify end-to-end | command + expected behavior |
Default flow
01 → 02 → 03
For user-reported bugs: 01 → 02 → 03 → 04
Smoke (05) is standalone: invoke it when validating that a CLI command or feature works for a real user, after a feature ships or before a release. It is not part of the 01 → 03 write flow.
Transversal rules
- File suffix must match tier:
*.unit.test.ts,*.integration.test.ts,*.e2e.test.ts. - Mock only ports (domain interfaces) — never mock use-case internals or adapter implementations.
- Test name = observable behaviour sentence; use nested
describeblocks not prefix separators. describe.concurrent()is forbidden in unit tests; required in E2E tests.- Zero real network, zero real machine state outside temp dirs in any automated test.
- Write the failing test FIRST for every bug fix.
- Smoke tests run the real built binary in a fresh
/tmpdir, never the repo root.
What ships with it
10 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.
- actions/01-pick-tier.md 1.3 KB
- actions/02-name-behaviorally.md 1.3 KB
- actions/03-write.md 1.7 KB
- actions/04-empirical-repro.md 1.4 KB
- actions/05-smoke.md 1.5 KB
- evals/scenarios.json 646 B
- references/bug-empirical-reproduction.md 1.7 KB
- references/golden-machine-independence.md 2.3 KB
- references/smoke-in-tmp.md 1.8 KB
- references/test-pyramid.md 1.8 KB
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 · 57 lines · 79 tokens per session scan A 2ed1770de247
test is a skill published in the GitHub repository ai-driven-dev/framework (445 stars, last pushed 2d ago), licensed MIT. It adds 79 tokens to every session and 723 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-08-30.
Other skills, from other repositories
smoke-test
End-to-end smoke test skill for DeerFlow. Guides through: 1) Pulling latest code, 2) Docker OR Local installation and deployment (user preference, default to Local if Docker network issues), 3) Service availability verification, 4) Health check, 5) Final test report. Use when the user says "run smoke test", "smoke…
image-generation
Use this skill when the user requests to generate, create, imagine, or visualize images including characters, scenes, products, or any visual content. Supports structured prompts and reference images for guided generation.
podcast-generation
Use this skill when the user requests to generate, create, or produce podcasts from text content. Converts written content into a two-host conversational podcast audio format with natural dialogue.
vercel-deploy
Deploy applications and websites to Vercel. Use this skill when the user requests deployment actions such as "Deploy my app", "Deploy this to production", "Create a preview deployment", "Deploy and give me the link", or "Push this live". No authentication required - returns preview URL and claimable deployment link.
zeroclaw
Help users operate and interact with their ZeroClaw agent instance — through both the CLI (zeroclaw commands) and the REST/WebSocket gateway API. Use this skill whenever the user wants to: send messages to ZeroClaw, manage memory or cron jobs, check system status, configure channels or providers, hit the gateway API…
github-issue-triage
Issue triage and lifecycle management agent for ZeroClaw. Use this skill whenever the user wants to: triage open issues, close stale/duplicate/fixed issues, apply labels, run a backlog sweep, enforce the current issue stale policy, or handle a specific issue. Trigger on: 'triage issues', 'issue triage', 'sweep…