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 Quinoto-Tech/QuinotoSpec --skill quinotospec-tddgit clone --depth 1 https://github.com/Quinoto-Tech/QuinotoSpecWrote 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/quinoto-tech/quinotospec/quinotospec-tdd)<a href="https://agentmods.dev/skills/quinoto-tech/quinotospec/quinotospec-tdd"><img src="https://agentmods.dev/badge/skills/quinoto-tech/quinotospec/quinotospec-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/quinoto-tech/quinotospec/quinotospec-tdd"><img src="https://agentmods.dev/badge/skills/quinoto-tech/quinotospec/quinotospec-tdd.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.00032 | $0.01288 |
| Opus 5.5 | $0.00013 | $0.00515 |
| Sonnet 5.5 | $0.00006 | $0.00258 |
| Haiku 4.5 | $0.00003 | $0.00129 |
Grade A, and why
quinotospec-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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: QuinotoSpec TDD
Iron Law
No escribas código de producción sin observar primero un test mínimo que falle por la razón esperada.
Una tarea de documentación, configuración o migración puede omitir TDD solo cuando el cambio no altera comportamiento ejecutable. En ese caso registra la justificación y usa una verificación apropiada.
RED-GREEN-REFACTOR
- RED: escribe un test mínimo para el comportamiento requerido y ejecútalo. Guarda comando, salida y motivo del fallo.
- GREEN: implementa solo lo necesario para que el test pase. No agregues capacidades futuras.
- REFACTOR: mejora nombres, estructura y duplicación sin cambiar comportamiento. Ejecuta nuevamente los tests afectados.
- Ejecuta la suite relevante y registra el resultado.
Evidencia mínima
Test: <ruta:test>
Comando: <comando>
Resultado RED: falló porque <razón esperada>
Comando GREEN: <comando>
Resultado GREEN: pasó
Suite: <comando y resultado>
Un test que falla por una importación rota, una configuración inválida o un error del entorno no cuenta como RED válido. Corrige el andamiaje y vuelve a observar el fallo funcional.
Registro verificable
Guarda un registro JSON en .quinoto-spec/evidence/{{TASK_ID}}/tdd.json con schema_version, task_id, recorded_at, expected_failure, observed_failure y los bloques red, green y suite. Cada bloque incluye command, status, exit_code y output.
python3 -B agent-dist/skills/quinotospec-rules-enforce/evidence_validate.py validate \
--root . --kind tdd --task-id {{TASK_ID}} --require --json
El validador comprueba estructura, tipos, exit codes y frescura; no ejecuta el comando por ti. Un registro stale o un RED con exit code 0 bloquea.
Matriz de aplicación
| Cambio | TDD | Evidencia mínima |
|---|---|---|
| Lógica de producción | Obligatorio | Test falla antes y pasa después |
| API o integración | Obligatorio | Test de contrato o regresión |
| Bug | Obligatorio | Test de regresión que reproduce el bug |
| Documentación | Opcional | Revisión de links, sintaxis y renderizado |
| Configuración | Condicional | Test de configuración o validación determinista |
| Migración | Obligatorio | Test de migración y datos preservados |
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 117 lines · 32 tokens per session scan A b1039e361174
quinotospec-tdd is a skill published in the GitHub repository Quinoto-Tech/QuinotoSpec (21 stars, last pushed yesterday), licensed MIT. It adds 32 tokens to every session and 1,288 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-09-26.
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.