test

A command for test-driven development, or TDD: writing a test that fails, implementing the behavior, and then checking that the test passes before refactoring. For bugs, it first adds a failing test that proves the problem.

In plain words
What is it for?
Use it to build new features, reproduce and fix bugs, run the full test suite for regressions, and verify browser-related fixes in a real browser.
Why use it?
It confirms the expected behavior before implementation and helps prevent the same bug from returning.

Command for Claude Code

Install

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.

agentmods
npx agentmods add commands/233i/agent-skills/test
Clone the repo
git clone --depth 1 https://github.com/233i/agent-skills

Made for: Claude Code.

Per session 25 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 186 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00025 $0.00186
Opus 5 $0.00013 $0.00093
Sonnet 5 $0.00005 $0.00037
Haiku 4.5 $0.00003 $0.00019

Measured 2d ago against content hash b77c358b4004, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

.claude/commands/test.md · 22 lines

What it actually says

调用 agent-skills:test-driven-development

对于新功能:

  1. 写出描述预期行为的测试,而且它们一开始应该失败
  2. 实现代码,让测试通过
  3. 在保持测试为绿的前提下重构

对于 bug 修复,也就是 Prove-It pattern:

  1. 先写一个能复现 bug 的测试,而且必须失败
  2. 确认这个测试确实失败
  3. 实现修复
  4. 确认测试通过
  5. 运行完整测试套件,检查回归

如果问题与浏览器相关,还要同时调用 agent-skills:browser-testing-with-devtools,用 Chrome DevTools MCP 做运行时验证。

Changes

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.

  1. 2d ago First seen · 22 lines · 25 tokens per session scan A b77c358b4004

Subscribe to this mod's changes

test is a command published in the GitHub repository 233i/agent-skills (6 stars, last pushed 4mo ago), licensed MIT. It adds 25 tokens to every session and 186 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.