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 e2e-protocolgit 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/e2e-protocol)<a href="https://agentmods.dev/skills/cruzs85/opencode-multiagente-local-37-iterations/e2e-protocol"><img src="https://agentmods.dev/badge/skills/cruzs85/opencode-multiagente-local-37-iterations/e2e-protocol.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.00022 | $0.00886 |
| Opus 5 | $0.00011 | $0.00443 |
| Sonnet 5 | $0.00004 | $0.00177 |
| Haiku 4.5 | $0.00002 | $0.00089 |
Grade A, and why
e2e-protocol 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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OBJETIVO
Garantizar validaciones E2E determinísticas evitando ciclos entre:
- @e2e-validator
- @code-writer
- @decomposer
REGLAS OBLIGATORIAS
1. Ownership único del fallo
Cada fallo detectado debe generar un único responsable:
- [ui-renderizado] → @code-writer
- [datos-incorrectos] → @code-writer
- [lógica-de-negocio] → @decomposer
PROHIBIDO reenviar el mismo fallo a diferentes agentes.
2. Fingerprint del fallo
Antes de delegar una corrección, generar un fingerprint:
Formato:
E2E::::::
Ejemplo:
E2E::login.spec.ts::should login::locator timeout button submit
Si el fingerprint reaparece:
- NO volver a delegar al mismo agente.
- Escalar inmediatamente.
LÍMITES DE ITERACIÓN
Regla estricta
Máximo:
- 1 corrección por @code-writer
- 1 análisis por @decomposer
Secuencia permitida:
- Ejecutar Playwright
- Detectar fallo
- Delegar UNA vez
- Reejecutar Playwright
- Si falla el MISMO fingerprint:
- TERMINAR
- Escalar
- NO reintentar
PROTOCOLO DE ESCALADO
Escalar a @decomposer SOLO si:
- El fallo es [lógica-de-negocio]
- O el mismo fingerprint reaparece tras corrección
Información obligatoria para escalado
Enviar SIEMPRE:
- archivo spec
- nombre del test
- mensaje completo
- stack trace
- screenshot exacto
- pasos reproducibles
- fingerprint
PROHIBICIONES
@e2e-validator NO puede:
- editar archivos
- sugerir cambios vagos
- reenviar errores sin fingerprint
- ejecutar más de 2 corridas Playwright por tarea
- delegar el mismo fingerprint dos veces
REGLA DE CIERRE
Si el mismo fingerprint persiste tras:
- 1 corrección
- 1 rerun
La tarea debe marcarse como:
ESTADO: BLOCKED CAUSA: Persistent E2E failure
y finalizar inmediatamente.
CRITERIO DE ÉXITO
Una validación E2E válida requiere:
- mínimo 1 ejecución real de Playwright
- máximo 2 ejecuciones
- ausencia de fingerprints repetidos
- evidencia de screenshot/log cuando exista fallo
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 · 173 lines · 22 tokens per session scan A 131f628938cd
e2e-protocol is a skill published in the GitHub repository cruzs85/opencode-multiagente-local-37-iterations (5 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 886 once invoked, about $0.0001 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
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
test-warp-ui
Guides testing Warp UI features and changes using the computer use tool. Use this skill only when computer-use testing was requested (explicit request or accepted offer) and the computeruse tool is available to the agent. Covers launching Warp and verifying UI behavior.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…
pyats-dynamic-test
Generate and execute deterministic pyATS aetest validation scripts - interface state, OSPF neighbors, BGP paths, ping matrices, and custom compliance tests. Use when writing a network test, validating post-change state, running pass/fail checks, or building automated regression tests.
test-loop
Plan, generate, and heal an executable E2E test suite from approved acceptance criteria (web and mobile).
playwright-cli
Automates browser interactions for testing and validating your own web applications using playwright-cli. Use when you need terminal-first browser control for navigation, form filling, screenshots, tracing, bound browser sessions, debugging, or generating Playwright test code. Only use against applications you own or…