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 hubertlim/SkillForge --skill tdd-workflowgit clone --depth 1 https://github.com/hubertlim/SkillForgeWrote 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/hubertlim/skillforge/tdd-workflow)<a href="https://agentmods.dev/skills/hubertlim/skillforge/tdd-workflow"><img src="https://agentmods.dev/badge/skills/hubertlim/skillforge/tdd-workflow/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/hubertlim/skillforge/tdd-workflow"><img src="https://agentmods.dev/badge/skills/hubertlim/skillforge/tdd-workflow.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.00018 | $0.00271 |
| Opus 5.5 | $0.00007 | $0.00108 |
| Sonnet 5.5 | $0.00004 | $0.00054 |
| Haiku 4.5 | $0.00002 | $0.00027 |
Grade A, and why
tdd-workflow 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 1mo 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
Step 1: 💡 Brainstorm
Generate and explore ideas before committing to a plan
- Gather requirements from the user
- List at least 3 possible approaches
- Evaluate trade-offs for each approach
- Recommend the best path forward with reasoning
Step 2: 📋 Plan
Create a structured implementation plan
- Break the task into discrete, ordered steps
- Identify dependencies between steps
- Define clear acceptance criteria
Step 3: 🧪 Test First (TDD)
Write tests before implementation code
- Write a failing test for the next requirement
- Implement the minimum code to make it pass
- Refactor while keeping tests green
- Repeat for each requirement
Step 4: ⚡ Implement
Write production code following best practices
- Follow the established plan step by step
- Write clean, idiomatic code
- Add inline comments for complex logic
- Keep functions small and focused
Step 5: 🔍 Code Review
Review code for quality, security, and correctness
- Check for security vulnerabilities
- Verify error handling is comprehensive
- Ensure consistent code style
- Validate that tests cover critical paths
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.
- 1mo ago First seen · 49 lines · 18 tokens per session scan A 0d8b791f6cfe
tdd-workflow is a skill published in the GitHub repository hubertlim/SkillForge (5 stars, last pushed 6mo ago), licensed MIT. It adds 18 tokens to every session and 271 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-31.
Other skills, from other repositories
bad-case-to-dpo
A guide to turning failed production agent runs into training and evaluation data. It explains how to find the first mistake, create preference examples for DPO (Direct Preference Optimization), and check that a fix does not damage other tasks.
engineering-workflow
A Chinese-language workflow for reliable software development. It describes exploring the problem, making a plan, using TDD (test-driven development, where tests are written before the code), debugging methodically, reviewing code, and verifying the result.
08-debug
Reproduce and fix a known bug, or find an unknown root cause by hypothesis validation. Use when the user wants to fix a bug, find why something breaks, or reopen a stuck investigation. Not for building a feature or reviewing a diff.
implement
Implement a technical design by decomposing it into dependency-ordered vertical slices, executing each with TDD red-green, reviewing each via an isolated sub-agent, and persisting progress to a state file so work survives session restarts. Use when the user has a tech design (doc or settled conversation) and says…
project-setup
One-time interactive setup to configure a project for autonomous development. Use when setting up a new project for TDD-based autonomous development with HCF.
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment.