A test-driven development guide that structures work as red, green, and refactor: write a failing test, make it pass, then improve the code.

Use it while implementing features or bug fixes, or while carrying out a specific planned task with test-driven development.

It keeps feature and bug-fix work focused on one behavior at a time and checks that the behavior works before moving on.

ward — Skill for Claude Code by Alexander-Tyagunov/magician

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.

Any agent

npx skills add Alexander-Tyagunov/magician --skill ward

Clone the repo

git clone --depth 1 https://github.com/Alexander-Tyagunov/magician

Made for: Claude Code.

Or install magician, the plugin that ships this one along with the rest of its 25 skills, 7 agents, 12 hooks.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/alexander-tyagunov/magician/ward/github.svg)](https://agentmods.dev/skills/alexander-tyagunov/magician/ward)

Your own site

<a href="https://agentmods.dev/skills/alexander-tyagunov/magician/ward"><img src="https://agentmods.dev/badge/skills/alexander-tyagunov/magician/ward/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/alexander-tyagunov/magician/ward"><img src="https://agentmods.dev/badge/skills/alexander-tyagunov/magician/ward.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,925 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00034	$0.01925
Opus 5.5	$0.00014	$0.00770
Sonnet 5.5	$0.00007	$0.00385
Haiku 4.5	$0.00003	$0.00193

Measured 5d ago against content hash b383630b0991, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

ward 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 5d 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.

skills/ward/SKILL.md · 76 lines

How it starts

The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/ward — TDD Engine

Enforce strict red → green → refactor discipline for all implementation work. (This skill absorbed the former /forge — general TDD and per-task blueprint execution are one engine.)

Match the project's conventions (read before you write)

Before implementing, discover and read the repo's own standards — CLAUDE.md, any code-review.md / CONTRIBUTING / STYLEGUIDE, and the linter/formatter config — and mirror the patterns already in the files you touch. Conventions a formatter can't enforce (async/await over .then, error-wrapping, naming, locale-code format) are still binding — apply them as you write, not after a reviewer flags them. See lore/code-standards.md.

Effort

Scale /effort to task size: low for a one-line fix, medium for normal work, high for a complex multi-behavior task (xhigh only for a genuinely hard multi-layer one; max is session-only and an opt-in for frontier problems). Across a run: medium for implementation turns, high for certify/review/security turns; on Bedrock/Vertex/gateways hold one level (an effort change drops the cache there). See lore/models.md.

The failing test is the verification. Don't add a self-review step after green — re-reading your own diff to confirm it is redundant on current models. Let RED → GREEN → REFACTOR and /certify carry the proof. See lore/model-behavior.md.

Autonomy — approve the plan, then run

Once the spec is settled — the failing test you can write, or the plan task in .workspace/shared/plans/ — run the remaining phases (RED → GREEN → REFACTOR and the per-task steps) autonomously: don't stop to ask the owner between phases before reading CLAUDE.md/standards, searching, kg query/blast, running the tests, or read-only git (git status, diff). This skill pre-approves only reads and read-only searches (Read, Grep, Glob and the embedded ugrep/bfs/rg/grep/find commands), because TDD edits arbitrary source and no honest path limit exists: kg lookups, test runs, and edits go through Claude Code's normal permission prompt unless the user runs in auto mode or approves them. Re-gate only on real side effects — the per-task git add/commit/push. Beyond that, pause only for genuine spec ambiguity (the "cannot write the test first" case below). See lore/autonomy.md.

Read the full file on GitHub · 76 lines

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.

5d ago Changed · -12 lines · -7 tokens per session b383630b0991
7d ago Changed · +2 lines ae71b7c38788
1mo ago Changed · +77 lines 412a739f52cd
2mo ago First seen · 9 lines · 41 tokens per session scan A 68f1aeb3be44

Subscribe to this mod's changes

ward is a skill published in the GitHub repository Alexander-Tyagunov/magician (14 stars, last pushed 6d ago), licensed MIT. It adds 34 tokens to every session and 1,925 once invoked, about $0.0001 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-30.

Claude Code TDD Testing agentic-ai ai-agents anthropic automation claude-plugin

ward next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
wardAlexander-Tyagunov/magician	Skill	14	6d ago	MIT	A	34	Claude Code
workflow-patternswshobson/agents	Skill	42k	today	MIT	A	35	Claude Code
tddmichael-denyer/pstack-claude	Skill	4.1k	yesterday	MIT	A	52	Claude Code
principle-test-behavior-not-implementationmichael-denyer/pstack-claude	Skill	4.1k	yesterday	MIT	A	50	Claude Code
dev-tddchristopherlouet/claude-base	Skill	5	8d ago	MIT	A	75	Claude Code
team-management-tdd-disciplineTeamManagementPlugin/claude-plugin	Skill	6	25d ago	MIT	A	96	Claude Code, Codex
tddpatforna/auto-task	Skill	11	2mo ago	MIT	A	72	Claude Code