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 TeamManagementPlugin/claude-plugin --skill team-management-tdd-disciplinegit clone --depth 1 https://github.com/TeamManagementPlugin/claude-pluginWrote 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/teammanagementplugin/claude-plugin/team-management-tdd-discipline)<a href="https://agentmods.dev/skills/teammanagementplugin/claude-plugin/team-management-tdd-discipline"><img src="https://agentmods.dev/badge/skills/teammanagementplugin/claude-plugin/team-management-tdd-discipline/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/teammanagementplugin/claude-plugin/team-management-tdd-discipline"><img src="https://agentmods.dev/badge/skills/teammanagementplugin/claude-plugin/team-management-tdd-discipline.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.00096 | $0.01054 |
| Opus 5 | $0.00048 | $0.00527 |
| Sonnet 5 | $0.00019 | $0.00211 |
| Haiku 4.5 | $0.00010 | $0.00105 |
Grade A, and why
team-management-tdd-discipline 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 8d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TDD When Applicable
Core Principle
Write the test first. Watch it fail. Write minimal code to pass.
If you didn't watch the test fail, you don't know it tests the right thing. Tests written after the code pass immediately — and passing immediately proves nothing: the test might assert the wrong behaviour, might test the implementation instead of the contract, might miss the cases you already forgot. Only a test you saw fail, for the reason you expected, is evidence of anything.
Applicability Matrix
TDD is a tool, not a loyalty oath. Forcing it where it does not fit produces ceremonial tests that assert nothing.
Applies to:
- Bug fixes — the failing test reproduces the bug, then the fix makes it pass. This proves the fix and leaves a regression guard behind.
- Behaviour changes — new required output, new validation, a changed contract.
- Feature work with clear inputs and outputs.
- Refactoring of already-tested code — the existing tests are the safety net.
Does not apply (do not force it):
- Exploratory spikes where the goal is learning, not shipping.
- Framework or config scaffolding (
setup.py, CI YAML,.gitignore, Dockerfile boilerplate). - One-off migration or analysis scripts, run once and discarded.
- Documentation-only changes.
- Pure refactoring with zero behaviour change where the existing suite already covers the surface — that suite is the oracle.
When uncertain which category applies, default to writing the test. The thirty seconds it takes to find out is almost always cheaper than the debugging session it replaces.
RED-GREEN-REFACTOR
RED — write the failing test
One test, one behaviour, a clear name, exercising real code. Be suspicious of a test that exercises mocks rather than the production path — it will pass forever regardless of the code.
Verify RED — watch it fail
Run it. Confirm three things:
- It fails, rather than erroring out from a typo or a bad import.
- The failure message is the one you expected.
- It fails because the behaviour is missing — not because of an unrelated bug elsewhere.
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.
- 8d ago First seen · 105 lines · 96 tokens per session scan A ef3518d84a42
team-management-tdd-discipline is a skill published in the GitHub repository TeamManagementPlugin/claude-plugin (5 stars, last pushed 1mo ago), licensed MIT. It adds 96 tokens to every session and 1,054 once invoked, about $0.0005 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
blueprint
Converts an approved spec into a TDD task plan with a parallelism map (PARALLEL vs SEQUENTIAL), saved to .workspace/shared/plans/. Use after a spec is approved, before implementation.
ward
TDD engine and enforcer — red/green/refactor, one behavior at a time. Use while implementing any feature or bugfix, or to execute a specific blueprint task with TDD.
mindforge-plan-phase_extended
Use when you have a spec or requirements for a multi-step task, before touching code.
atdd-plan
Produce an ATDD-first implementation plan in Claude Code's native plan mode, with named design patterns called out where they earn their keep. The skill enters plan mode automatically (via the EnterPlanMode tool), runs /flagrare:codebase-explore to ground the plan in the actual codebase, then produces a plan-mode plan…
tdd
Strict TDD workflow (Red-Green-Refactor).
mindforge-tdd_extended
Use when implementing any feature or bugfix, before writing implementation code.