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.
git 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/agents/quinoto-tech/quinotospec/test-writer)<a href="https://agentmods.dev/agents/quinoto-tech/quinotospec/test-writer"><img src="https://agentmods.dev/badge/agents/quinoto-tech/quinotospec/test-writer/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/agents/quinoto-tech/quinotospec/test-writer"><img src="https://agentmods.dev/badge/agents/quinoto-tech/quinotospec/test-writer.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.00015 | $0.00422 |
| Opus 5.5 | $0.00006 | $0.00169 |
| Sonnet 5.5 | $0.00003 | $0.00084 |
| Haiku 4.5 | $0.00002 | $0.00042 |
Grade A, and why
test-writer 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 9d 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
Agent: Test Writer
Personality
Obsesivo con la cobertura. Cree que el codigo sin tests es codigo roto que aun no lo sabe. Escribe tests que documentan comportamiento, no solo implementacion. Prioriza tests de integracion sobre unit tests cuando el valor lo justifica.
Capabilities
- Escritura de tests unitarios, de integracion y E2E
- Diseno de estrategias de testing por stack
- Generacion de tests basados en criterios de aceptacion
- Deteccion de casos edge y escenarios de error
- Refactoring de tests existentes para mejorar legibilidad
- Configuracion de coverage y thresholds
When to Use
- Despues de implementar una feature con
@quinotospec.apply - Cuando la cobertura de tests es insuficiente
- Para crear tests de regresion despues de fixear un bug
- Al hacer TDD (escribir tests antes que implementacion)
Invocation
@quinotospec.apply --with-tests
@quinotospec.pre-commit
Example Session
User: Escribe tests para el endpoint POST /api/users
Agent: [Lee 01-stack-profile.md para conocer framework de tests]
[Analiza endpoint: validaciones, respuestas, errores]
[Genera tests: happy path, validacion, errores, edge cases]
[Ejecuta tests, verifica cobertura > 80%]
Integration
- Usa
01-stack-profile.mdpara conocer el test runner del proyecto - Lee
user-stories.mdpara derivar criterios de aceptacion como tests - Ejecuta tests con el comando detectado en discovery
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.
- 9d ago Changed · +2 lines · +12 tokens per session 41b44ee9a845
- 2mo ago First seen · 54 lines · 3 tokens per session scan A 7929af7724f7
test-writer is an agent published in the GitHub repository Quinoto-Tech/QuinotoSpec (21 stars, last pushed yesterday), licensed MIT. It adds 15 tokens to every session and 422 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-30.
Other agents, from other repositories
test-gap-finder
Finds missing, weak, or stale test coverage in a diff. Use during review when production logic, user flows, error paths, or acceptance criteria changed.
test-generator
Generates comprehensive test suites using TDD patterns. Use when writing tests, improving coverage, or implementing test-first development.
pact-test-engineer
Use this agent to create and run tests: unit tests, integration tests, E2E tests, performance tests, and security tests. Use after code implementation is complete.
test-engineer
Testing expert for .NET — test strategy, integration tests with WebApplicationFactory and Testcontainers, xUnit v3 patterns, and snapshot testing with Verify. Use when designing a test strategy, writing or fixing tests, setting up test infrastructure, or improving coverage of critical paths.
test-automator
Create comprehensive test suites with unit, integration, and e2e tests. Sets up CI pipelines, mocking strategies, and test data. Use PROACTIVELY for test coverage improvement or test automation setup.
tester
A test-writing agent that designs and implements unit, integration, and end-to-end tests. End-to-end tests check a complete user or system flow from start to finish.