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/allgpt-co/quickvoice/tddnpx skills add allgpt-co/QuickVoice --skill tddgit clone --depth 1 https://github.com/allgpt-co/QuickVoiceWrote 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/allgpt-co/quickvoice/tdd)<a href="https://agentmods.dev/skills/allgpt-co/quickvoice/tdd"><img src="https://agentmods.dev/badge/skills/allgpt-co/quickvoice/tdd.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.1 | $0.00015 | $0.00170 |
| Opus 5 | $0.00008 | $0.00085 |
| Sonnet 5 | $0.00003 | $0.00034 |
| Haiku 4.5 | $0.00002 | $0.00017 |
Grade A, and why
gsd:reference:tdd 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 6d 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
GSD TDD Reference
Test-Driven Development patterns and practices.
When to Use
- Writing new functionality
- Refactoring existing code
- Ensuring test coverage
TDD Cycle
- Red - Write failing test
- Green - Make test pass
- Refactor - Improve code
Best Practices
- Write smallest test first
- Test one thing at a time
- Use descriptive test names
- Maintain fast test execution
- Achieve high coverage
Success Criteria
Tests written before implementation, all passing.
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.
- 6d ago First seen · 36 lines · 15 tokens per session scan A 2fa0eb78a0ee
gsd:reference:tdd is a skill published in the GitHub repository allgpt-co/QuickVoice (491 stars, last pushed 24d ago), licensed MIT. It adds 15 tokens to every session and 170 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-30.
Other skills, from other repositories
pest-testing
Use this skill for Pest PHP testing in Laravel projects only. Trigger whenever any test is being written, edited, fixed, or refactored — including fixing tests that broke after a code change, adding assertions, converting PHPUnit to Pest, adding datasets, and TDD workflows. Always activate when the user asks how to…
test-guide
Test-writing guide for Backend.AI — propose success/exception/edge scenarios first, refine them with the user, then implement while reporting per-scenario verification status. Covers fixtures, withtables, mock repositories, pants test, optional TDD cadence.
代码调试
调试工作流：确认需要 → 先写失败测试复现 → 定位根因 → 修复 → 回归。含修复熔断机制（同模块 bug 打回超 3 次停止）、逐层根因分析（5 Whys）、假设管理、鱼骨图。用于 Bug 修复、测试失败、运行时错误排查。.
lumina-backend-api
Implement and debug the Express and TypeScript backend for Lumina. Use when editing files under server/src or server/package.json, changing authentication, conversations, guest flows, chat routes, models, middleware, API contracts, or Gemini and Pinecone service wiring outside the dedicated knowledge-ingestion…
lumina-frontend-ui
Build, refine, and debug the React/Vite frontend for Lumina. Use when editing files under client/src or client/package.json, changing chat UX, landing page content, auth flows, routing, theme behavior, markdown rendering, animations, responsive layout, or frontend API wiring.
lumina-rag-knowledge
Manage Lumina's retrieval-augmented generation and knowledge ingestion workflow. Use when editing server/src/services/knowledgeBase.ts, server/src/services/pineconeClient.ts, server/src/scripts/knowledgeCli.ts, server/src/models/KnowledgeSource.ts, files under server/knowledge, manifest-based sync inputs, or debugging…