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 FacturaScripts/fs-claude-plugin --skill analizar-buggit clone --depth 1 https://github.com/FacturaScripts/fs-claude-pluginWrote 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/facturascripts/fs-claude-plugin/analizar-bug)<a href="https://agentmods.dev/skills/facturascripts/fs-claude-plugin/analizar-bug"><img src="https://agentmods.dev/badge/skills/facturascripts/fs-claude-plugin/analizar-bug.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00190 | $0.00987 |
| Opus 5 | $0.00095 | $0.00494 |
| Sonnet 5 | $0.00038 | $0.00197 |
| Haiku 4.5 | $0.00019 | $0.00099 |
Grade A, and why
analizar-bug 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: analizar-bug — Localización y corrección de bugs en FacturaScripts
Esta skill orquesta los agentes especializados para localizar, entender y corregir bugs en plugins de FacturaScripts de forma sistemática, garantizando que la corrección sea coherente con los patrones del framework y quede cubierta por un test.
Por qué usar agentes en lugar de investigar directamente
Cuando hay un bug, la tentación es leer el código directamente y arreglarlo. Pero sin el contexto del framework es fácil:
- Confundir comportamiento correcto de FacturaScripts con el bug
- Arreglar el síntoma sin entender la causa raíz
- Introducir una corrección que rompe otro comportamiento del framework
- Escribir el test de verificación sin conocer los patrones de test del ERP
Los agentes especializados evitan estos errores porque conocen los patrones del ERP.
Flujo de análisis de bugs
Paso 1 — Entender el comportamiento esperado (docs-expert)
Antes de mirar el código incorrecto, entender qué debería hacer según el framework:
Agente: docs-expert
Tarea: ¿Cómo debería funcionar [módulo/clase afectado] en FacturaScripts?
Busca documentación sobre [concepto involucrado: Asiento, Ejercicio, Subcuenta,
getSubcuenta, codejercicio, modelo afectado, etc.].
Paso 2 — Analizar y corregir el código (backend-developer)
Con el comportamiento esperado claro, buscar la causa raíz en el código:
Agente: backend-developer
Tarea: Analiza el bug en [archivo/método]. El comportamiento esperado es [X],
pero el comportamiento real es [Y]. Lee el código en [ruta] y localiza
la causa raíz. Propón y aplica la corrección mínima necesaria sin
introducir cambios fuera del alcance del bug.
Paso 3 — Escribir un test que verifique la corrección (testing-expert)
Una vez corregido, un test que habría fallado antes de la corrección y pasa después:
Agente: testing-expert
Tarea: Escribe un test PHPUnit que reproduzca el bug corregido:
[descripción del caso]. El test debe verificar [comportamiento correcto].
Añádelo en [archivo de test existente: Test/main/XxxTest.php].
Sigue los patrones del proyecto: DefaultSettingsTrait, RandomDataTrait,
LogErrorsTrait y los helpers existentes del test.
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 · 94 lines · 190 tokens per session scan A 55b01e2f1f8b
analizar-bug is a skill published in the GitHub repository FacturaScripts/fs-claude-plugin (8 stars, last pushed 5d ago), licensed MIT. It adds 190 tokens to every session and 987 once invoked, about $0.0010 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.