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/joaonic/agentkit/tdd-workflownpx skills add Joaonic/agentkit --skill tdd-workflowgit clone --depth 1 https://github.com/Joaonic/agentkitWhat 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.00049 | $0.01674 |
| Opus 5 | $0.00024 | $0.00837 |
| Sonnet 5 | $0.00010 | $0.00335 |
| Haiku 4.5 | $0.00005 | $0.00167 |
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 yesterday.
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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TDD Workflow (Test-Driven Development)
Quando usar (sempre)
- Mudança de comportamento (feature nova, correção de bug com regressão) — ver
04-tdd-mandatory.mdcedocs/governance/cursor/workflow/00-overview.md(test-first). - Quando existe um alvo verificável (testes) para iterar até passar.
Antes do primeiro teste
- Cumprir investigação mínima — rule
01-investigation-before-implementation.mdc; objetivos/non-objectivos; módulos e contratos impactados; evitar duplicar use cases/adapters/UI já existentes. - Se o escopo tocar
apps/*,web/*,libraries/*,infra/*: lerAGENTS.mde README do subprojeto (quando existirem) — comandos e camadas corretas (40-submodule-governance.mdc). - Ordem de fases em execução guiada:
docs/governance/cursor/workflow/02-implementation.md(investigation → TDD prep → implementation loop → …).
Fluxo TDD (disciplina)
- Escrever ou estender testes primeiro — cenários e asserts claros; nomes que documentem comportamento.
- Executar a suíte relevante e confirmar falha — não adicionar implementação “para fazer passar” antes de ver o vermelho (exceto infra mínima impossível de testar sem stubs já aceites no projeto).
- Implementar o mínimo para verde — sem alterar o contrato dos testes salvo erro de especificação já acordado com o utilizador.
- Refatorar com testes verdes (opcional mas recomendado).
- Repetir até cobrir acceptance criteria.
Regras
- Não usar mocks que substituam comportamento que ainda não existe de forma a falsificar verde — o primeiro objetivo é falha legítima.
- Não mudar testes durante implementação só para “facilitar” — se o teste estiver errado, corrigir com explícito acordo sobre especificação.
- Rodar testes após cada iteração significativa.
- Backend: integração com persistência realista → preferir Testcontainers + PostgreSQL onde o projeto já o faz (
15-database-flyway-testcontainers.mdc); não usar H2 para substituir semântica PostgreSQL em integração.
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.
- yesterday First seen · 94 lines · 49 tokens per session scan A ef748de1adc3
tdd-workflow is a skill published in the GitHub repository Joaonic/agentkit (2 stars, last pushed 3mo ago), licensed MIT. It adds 49 tokens to every session and 1,674 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.