Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/andregusman-raiz/a-gusman-claudenpx agentmods add skills/andregusman-raiz/a-gusman-claude/ag-referencia-tddWrote 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/andregusman-raiz/a-gusman-claude/ag-referencia-tdd)<a href="https://agentmods.dev/skills/andregusman-raiz/a-gusman-claude/ag-referencia-tdd"><img src="https://agentmods.dev/badge/skills/andregusman-raiz/a-gusman-claude/ag-referencia-tdd/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/andregusman-raiz/a-gusman-claude/ag-referencia-tdd"><img src="https://agentmods.dev/badge/skills/andregusman-raiz/a-gusman-claude/ag-referencia-tdd.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 4 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
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.00044 | $0.03293 |
| Opus 5.5 | $0.00018 | $0.01317 |
| Sonnet 5.5 | $0.00009 | $0.00659 |
| Haiku 4.5 | $0.00004 | $0.00329 |
Grade A, and why
ag-referencia-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 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.
How it starts
The opening of the file, as written. The whole thing — 319 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TDD Canonico — Red-Green-Refactor
Principio fundamental: escrever o teste que falha ANTES de existir implementacao. O teste define o comportamento desejado; a implementacao e consequencia.
Escopo: compoe com ~/Claude/CLAUDE.md (workspace) e CLAUDE.md local do projeto.
Quando carregar: ao usar /ag-1-construir --tdd, antes de implementar feature em dominio sensivel, ao fazer refactor de logica critica com suite de testes existente.
Pipeline Obrigatorio: 3 Fases por Ciclo
Fase RED — Escrever o teste que falha
- Ler a SPEC (ou criterio de aceite) do comportamento desejado
- Escrever o(s) teste(s) que cobrem exatamente esse comportamento
- Rodar os testes e CONFIRMAR que falham — se passarem sem implementacao, o teste esta errado (assertion fraca ou cobrindo comportamento ja existente)
- O erro de falha deve ser o erro esperado (ex:
TypeError: func is not defined, naoAssertionErrorvazio)
Checklist RED:
- Teste escrito antes de qualquer implementacao nova
- Rodei os testes e confirmei falha com mensagem de erro coerente
- O teste cobre o COMPORTAMENTO (entrada → saida esperada), nao a implementacao interna
- Commit de teste:
test: red — <descricao do comportamento>
Fase GREEN — Implementar o minimo para passar
- Escrever o codigo mais simples possivel que faz o teste passar
- Nao mais que o necessario — resistir a tentacao de generalizar ou otimizar agora
- Rodar os testes e confirmar que passam (todos, incluindo os anteriores)
- Se quebraram testes anteriores: o design esta errado — corrigir sem alterar os testes
Checklist GREEN:
- Implementei apenas o necessario para os testes novos passarem
- Todos os testes anteriores continuam passando (sem regressao)
- Nao adicionei logica especulativa ("pode ser util depois")
- Commit de implementacao:
feat: green — <descricao do comportamento>
Fase REFACTOR — Melhorar sem quebrar
- Com todos os testes verdes, melhorar a qualidade do codigo
- Extrair duplicacoes, renomear para clareza, simplificar estrutura
- Rodar os testes apos cada mudanca de refactor — qualquer falha = refactor errado, reverter
- Nunca refatorar sem suite verde — o risco de introducao silenciosa de bug e alto
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 · 319 lines · 44 tokens per session scan A acfadf35db60
ag-referencia-tdd is a skill published in the GitHub repository andregusman-raiz/a-gusman-claude (18 stars, last pushed 1mo ago), licensed MIT. It adds 44 tokens to every session and 3,293 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
engram-testing-coverage
TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.
principle-test-behavior-not-implementation
Apply when you write, change, or keep a test. Assert what the code's users can observe, so that the test fails when that behavior breaks and keeps passing when only the internals change.
conductor-implement
Execute tasks from a track's implementation plan following TDD workflow.
tdd
This skill should be used when the user wants to implement features or fix bugs using test-driven development. Enforces the RED-GREEN-REFACTOR cycle with vertical slicing, context isolation between test writing and implementation, human checkpoints, and auto-test feedback loops. Uses multi-agent orchestration with the…
mobiai-mobile-tdd
You MUST use this before writing any implementation code for a mobile feature, bug fix, refactor, or behavior change. Tests come before implementation — no exceptions.
iterative-development
TDD iteration loops using Claude Code Stop hooks - runs tests after each response, feeds failures back automatically.