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 explorer-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/explorer-protocol)<a href="https://agentmods.dev/skills/cruzs85/opencode-multiagente-local-37-iterations/explorer-protocol"><img src="https://agentmods.dev/badge/skills/cruzs85/opencode-multiagente-local-37-iterations/explorer-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.00021 | $0.00916 |
| Opus 5 | $0.00010 | $0.00458 |
| Sonnet 5 | $0.00004 | $0.00183 |
| Haiku 4.5 | $0.00002 | $0.00092 |
Grade A, and why
explorer-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 — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OBJETIVO
Explorar exclusivamente el codebase LOCAL del proyecto sin generar loops, crawling web ni exploraciones infinitas.
REGLAS OBLIGATORIAS
Exploración local únicamente
La exploración debe limitarse a:
- archivos locales
- estructura del proyecto
- dependencias internas
- flujos de datos
- puntos de edición
PROHIBICIONES
PROHIBIDO usar webfetch para:
- documentación de frameworks
- documentación OpenCode
- documentación Angular
- troubleshooting
- búsqueda general
- crawling automático
WEBFETCH SOLO PERMITIDO SI:
La tarea menciona explícitamente:
- API externa
- documentación externa
- integración de terceros
- RFC
- SDK externo
Si no existe una mención explícita:
- NO usar webfetch.
ORDEN OBLIGATORIO DE EXPLORACIÓN
Paso 1
Identificar:
- AGENTS.md
- package.json
- angular.json
- tsconfig.json
Paso 2
Mapear:
- src/
- apps/
- libs/
- shared/
Paso 3
Identificar:
- componentes relevantes
- servicios relacionados
- rutas
- stores/signals
- dependencias
REGLA ANTI-LOOP
Límites máximos
- máximo 20 toolcalls
- máximo 15 archivos inspeccionados
- máximo 5 búsquedas consecutivas
- máximo 1 reexploración de la misma ruta
Fingerprint de exploración
Toda exploración debe generar:
EXPLORER::::
Ejemplo:
EXPLORER::mapa::src/app/features/map
Si el mismo fingerprint reaparece:
- TERMINAR
- NO repetir exploración
- solicitar aclaración
REGLA ANTI-LOOP EN BÚSQUEDAS SIN RESULTADOS
Límite de búsquedas consecutivas con 0 resultados
- Máximo: 2 búsquedas consecutivas que retornen 0 resultados
- Si 2 búsquedas consecutivas retornan 0 resultados:
- TERMINAR inmediatamente la búsqueda
- Concluir que la característica NO existe en el código actual
- Reportar explícitamente: "La característica [X] no existe en el codebase"
- Solicitar aclaración al usuario si esto es inesperado
PROHIBICIÓN DE REPETICIÓN
ESTRICTAMENTE PROHIBIDO repetir la misma búsqueda si:
- La búsqueda anterior retornó 0 resultados
- Los patrones de búsqueda son idénticos o semánticamente equivalentes
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 · 200 lines · 21 tokens per session scan A 7940391dd746
explorer-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 21 tokens to every session and 916 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
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.