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 post-implementationgit 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/post-implementation)<a href="https://agentmods.dev/skills/cruzs85/opencode-multiagente-local-37-iterations/post-implementation"><img src="https://agentmods.dev/badge/skills/cruzs85/opencode-multiagente-local-37-iterations/post-implementation.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.00057 | $0.00861 |
| Opus 5 | $0.00028 | $0.00430 |
| Sonnet 5 | $0.00011 | $0.00172 |
| Haiku 4.5 | $0.00006 | $0.00086 |
Grade A, and why
post-implementation 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 7d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Post-Implementation Protocol
Objetivo
Verificar que los cambios implementados por code-writer son correctos ANTES de pasar a la fase de QA. Esto evita ciclos innecesarios de build fallidos.
Cuándo usarla
Después de que code-writer complete un lote de escritura de archivos, y ANTES de delegar a qa-validator.
Flujo de verificación
Paso 1: Delegar a @explorer
Pide a @explorer que verifique los siguientes puntos sobre los archivos modificados:
a. Código huérfano
- Métodos, variables o imports que hayan quedado sin callsite
- Código eliminado que haya dejado referencias rotas
- Listeners, imports o props que ya no se usen
b. Contratos entre archivos
- Los nombres de métodos, propiedades, tipos e interfaces sean consistentes entre los archivos modificados y los que dependen de ellos
- Ej: si se añadió una nueva signal pública en un servicio, el componente que la consume debe tener el import y la referencia correcta
c. Boilerplate Angular
standalone: trueen todos los componentesstyleUrl(singular, nostyleUrls)- APIs del navegador (window, document, canvas) usadas SOLO dentro de
afterNextRender - Inyección de dependencias con
inject(), no por constructor
d. Game loop (si aplica)
deltaTimepara movimientos frame-independientes (si se usa)- Coordenadas Y consistentes con el sistema de coordenadas del canvas
e. Integración servicio-componente (si aplica) Si el lote incluye un servicio con lógica de negocio y un componente que lo consume, indica a @explorer que cargue la skill 'integration-verification' y siga sus 5 pasos para verificar la cadena de llamadas completa, detectar métodos huérfanos y validar el flujo de datos desde el evento de usuario hasta la actualización visual.
Paso 2: Recibir y clasificar el reporte
Cuando @explorer responda, clasifica cada hallazgo:
| Clasificación | Significado | Acción |
|---|---|---|
| Falso positivo | El hallazgo no es un bug real (ej: explorer malinterpretó la lógica) | Ignorar, continuar |
| Bug real | Hay un error real en la implementación | Delegar a @code-writer con el detalle exacto |
| Estructural | El problema requiere rediseño o reorganización de archivos | Delegar a @decomposer para re-planificar |
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.
- 7d ago First seen · 74 lines · 57 tokens per session scan A 8e16ccdba790
post-implementation is a skill published in the GitHub repository cruzs85/opencode-multiagente-local-37-iterations (5 stars, last pushed 1mo ago), licensed MIT. It adds 57 tokens to every session and 861 once invoked, about $0.0003 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…