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 cruzs85/opencode-multiagente-local-37-iterations --skill unit-testinggit clone --depth 1 https://github.com/cruzs85/opencode-multiagente-local-37-iterationsWrote 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/cruzs85/opencode-multiagente-local-37-iterations/unit-testing)<a href="https://agentmods.dev/skills/cruzs85/opencode-multiagente-local-37-iterations/unit-testing"><img src="https://agentmods.dev/badge/skills/cruzs85/opencode-multiagente-local-37-iterations/unit-testing.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.00047 | $0.00965 |
| Opus 5 | $0.00023 | $0.00483 |
| Sonnet 5 | $0.00009 | $0.00193 |
| Haiku 4.5 | $0.00005 | $0.00097 |
Grade A, and why
unit-testing 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 8d 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OBJETIVO
Garantizar la correcta verificación de la lógica del código mediante pruebas unitarias, manejando tres escenarios:
- Crear tests cuando no existen
- Ejecutar tests cuando ya existen
- Diagnosticar fallos y determinar si son del test o de la implementación
REGLAS OBLIGATORIAS
1. Verificación de existencia
Antes de cualquier acción, verificar si el archivo .spec.ts existe:
find src/app -name "<nombre>.spec.ts" 2>/dev/null
2. Si NO existe → CREAR
Delegar a @code-writer la creación del archivo .spec.ts con:
- Estructura:
describe(),beforeEach()con TestBed.configureTestingModule,it()para cada caso - Cobertura mínima:
- 1 caso feliz (happy path)
- 1 caso borde (edge case)
- 1 caso de error (si aplica)
- Para servicios: Usar
TestBed.inject()+inject()de Angular - Para componentes: Configurar TestBed con standalone: true, imports necesarios
- Para signals: Verificar valores con
signal()yset(), probarcomputed()yeffect() - Estilo: Usar
fakeAsync()ytick()para operaciones asíncronas - Ubicación: Mismo directorio que el archivo de producción
3. Si SÍ existe → EJECUTAR
npm test -- --testPathPattern=<nombre>.spec.ts
4. Si EJECUCIÓN FALLA → DIAGNOSTICAR
Reglas de diagnóstico:
| Síntoma | Causa | Acción |
|---|---|---|
Property 'X' does not exist on type 'Y' |
El test usa una API que cambió | Fallo del test → modificar .spec.ts |
Expected X to equal Y donde X es valor real incorrecto |
La implementación devuelve valor incorrecto | Fallo de implementación → corregir producción |
Cannot read property of undefined en el test |
Mock incompleto o datos mal formados | Fallo del test → actualizar mocks |
Timeout - Async callback |
Operación asíncrona no resuelta | Fallo del test → ajustar fakeAsync/tick |
| Error de compilación TypeScript en el spec | Firma de método desactualizada en test | Fallo del test → actualizar firma |
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.
- 8d ago First seen · 121 lines · 47 tokens per session scan A e3037f84b70d
unit-testing is a skill published in the GitHub repository cruzs85/opencode-multiagente-local-37-iterations (5 stars, last pushed 1mo ago), licensed MIT. It adds 47 tokens to every session and 965 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
migrate-xunit-to-xunit-v3
Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest…
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
nw-fp-clojure
Clojure language-specific patterns, data-first modeling, REPL-driven development, and spec.
mobiai-ios-testing
Use when writing or running tests in an iOS project — unit tests, UI tests, snapshot tests, choosing the right framework.
restore-internals-seams-in-finally-blocks-after-each-test
When delegating a task affected by this skill, include.
testing-llm
LLM and AI testing patterns — mock responses, evaluation with DeepEval/RAGAS, structured output validation, and agentic test patterns (generator, healer, planner). Use when testing AI features, validating LLM outputs, or building evaluation pipelines.