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 hackerFish/awesome-dsh-skills --skill dsh-test-firstgit clone --depth 1 https://github.com/hackerFish/awesome-dsh-skillsWrote 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/hackerfish/awesome-dsh-skills/dsh-test-first)<a href="https://agentmods.dev/skills/hackerfish/awesome-dsh-skills/dsh-test-first"><img src="https://agentmods.dev/badge/skills/hackerfish/awesome-dsh-skills/dsh-test-first/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/hackerfish/awesome-dsh-skills/dsh-test-first"><img src="https://agentmods.dev/badge/skills/hackerfish/awesome-dsh-skills/dsh-test-first.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.00028 | $0.00286 |
| Opus 5 | $0.00014 | $0.00143 |
| Sonnet 5 | $0.00006 | $0.00057 |
| Haiku 4.5 | $0.00003 | $0.00029 |
Grade A, and why
dsh-test-first 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 10d 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.
What it actually says
测试优先（红 → 绿 → 重构）
流程
- 红：先写一个描述期望行为的测试，运行确认它失败（证明测试真的在测）
- 绿：写最小实现让测试通过，不做任何多余设计
- 重构：在绿灯下改善结构，每步都保持测试通过
边界用例表（写测试时逐项过）
- 空输入、单元素、满容量
- 错误类型、缺字段、超长输入
- 重复调用、并发调用
- 权限不足、文件不存在、网络失败
运行
- Node 内置：
node --test - 项目用 vitest/jest 时跟随项目配置
- 只测公共行为，不测内部实现细节；覆盖率数字不设硬指标，关键路径必须覆盖
修复 bug 的额外要求
先写一个能复现该 bug 的失败测试，再修复；提交信息里写清复现路径。
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.
- 10d ago First seen · 31 lines · 28 tokens per session scan A 1156ea2c728c
dsh-test-first is a skill published in the GitHub repository hackerFish/awesome-dsh-skills (5 stars, last pushed 5d ago), licensed MIT. It adds 28 tokens to every session and 286 once invoked, about $0.0001 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-31.
Other skills, from other repositories
test-first
A test-first development guide, where tests are written before the code they check. TDD, or test-driven development, means first writing a test that fails, then writing the simplest code that makes it pass.
tdd
A test-driven development workflow, where you write a test for one behavior, make it pass, and then improve the code while keeping the test.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code.
writing-skills
A guide for creating and testing reusable instructions for AI agents, called skills. It applies test-driven development, or TDD—the practice of writing tests before implementation—to instruction documents.
test-driven-development
Test-driven development, or TDD, is a way to build software by writing a test that fails, adding the smallest code that makes it pass, and then cleaning up the code. These instructions require that process for features, bug fixes, refactors, and behavior changes.
tdd
Guidance for test-driven development (TDD), a method where you write a failing test, make it pass with a small change, and then improve the code. It focuses on tests that check user-visible behavior through public interfaces.