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/jpm1118/threadwork/beads-tdd-executionnpx skills add JPM1118/Threadwork --skill beads-tdd-executiongit clone --depth 1 https://github.com/JPM1118/ThreadworkWrote 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/jpm1118/threadwork/beads-tdd-execution)<a href="https://agentmods.dev/skills/jpm1118/threadwork/beads-tdd-execution"><img src="https://agentmods.dev/badge/skills/jpm1118/threadwork/beads-tdd-execution.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.01937 |
| Opus 5 | $0.00000 | $0.00968 |
| Sonnet 5 | $0.00000 | $0.00387 |
| Haiku 4.5 | $0.00000 | $0.00194 |
Grade A, and why
beads-tdd-execution 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 4d 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 — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Beads TDD Execution Skill
Execute a single task from a Beads-backed plan using Test-Driven Development (RED-GREEN-REFACTOR flow).
When to Use This Skill
Use this skill when:
- There's a task ready for implementation (
bd readyreturns a task) - You're implementing work from a Beads-backed plan
- The task has clear acceptance criteria and design
Who Uses This Skill
This skill is used by:
- Subagents dispatched by the orchestrator to implement tasks
- The main agent when working directly on a task
Key constraint: If you're a subagent, you NEVER create new issues. Report discoveries back to the orchestrator.
Prerequisites
- Threadwork initialized
- A Beads-backed plan exists with tasks
- At least one task is ready (
bd readyreturns a task ID)
The TDD Flow: RED → GREEN → REFACTOR
Overview
┌─────────────────────────────────────────────────────────────┐
│ TDD Execution Flow │
├─────────────────────────────────────────────────────────────┤
│ │
│ 1. READ TASK bd --no-daemon show {task-id} │
│ ↓ │
│ 2. RED Write failing test │
│ ↓ Run test → confirm it fails │
│ 3. GREEN Write minimal implementation │
│ ↓ Run test → confirm it passes │
│ 4. REFACTOR Clean up code │
│ ↓ Run test → confirm still passes │
│ 5. NOTES Update progress in Beads │
│ ↓ │
│ 6. REPORT Report completion to orchestrator │
│ │
└─────────────────────────────────────────────────────────────┘
Skill Workflow
Step 1: Get the Ready Task
# Find what's ready to work on
bd --no-daemon ready
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.
- 4d ago First seen · 287 lines · 0 tokens per session scan A e55464e71f7f
beads-tdd-execution is a skill published in the GitHub repository JPM1118/Threadwork (5 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,937 tokens. 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
tdd
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
test-first-bugs
Enforces a test-driven bug-fixing workflow. Use when a user reports a bug, failing code, an error, or asks to fix something.
tdd
Test-driven development (TDD) process used when writing code. Use whenever you are adding any new code, unless the user explicitly asks to skip TDD or the code is exploratory/spike.
growing-outside-in-systems
Drive feature development using Outside-In TDD with Hexagonal Architecture. Design emerges through inline code, in-memory fakes, interface extraction, and deferred I/O. Use when building features, writing tests, or structuring backend services. Triggers on: TDD, outside-in, hexagonal, ports and adapters, emergent…
plan-create
Create structured implementation plans for autonomous TDD development. Use for new features, multi-file changes, or anything requiring multiple steps or tests. Triggers on aspirational openers ("let's build", "let's start building", "I want to make", "I want an app that", "help me build"), capability lists ("users…
red-green-refactor
Guides the red-green-refactor TDD workflow: write a failing test first, implement the minimum code to make it pass, then refactor while keeping tests green. Use when a user asks to practice TDD, write tests first, follow red-green-refactor, do test-driven development, write failing tests before code, or phrases like…