Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add FacturaScripts/fs-claude-plugin/plugin install fs-devWrote 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/verificar-min-version)<a href="https://agentmods.dev/skills/facturascripts/fs-claude-plugin/verificar-min-version"><img src="https://agentmods.dev/badge/skills/facturascripts/fs-claude-plugin/verificar-min-version/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/facturascripts/fs-claude-plugin/verificar-min-version"><img src="https://agentmods.dev/badge/skills/facturascripts/fs-claude-plugin/verificar-min-version.svg" alt="Reviewed on agentmods" width="80" 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.01765 |
| Opus 5.5 | $0.00023 | $0.00706 |
| Sonnet 5.5 | $0.00011 | $0.00353 |
| Haiku 4.5 | $0.00006 | $0.00177 |
Grade A, and why
verificar-min-version 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 10d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auditoría de compatibilidad y seguridad de un plugin
La auditoría tiene dos partes independientes: la compatibilidad con el core (min_version) y la seguridad (qué hace el plugin en el servidor y en el navegador). Haz las dos salvo que el usuario pida solo una. La de seguridad no necesita el clon del core: si falta, hazla igualmente.
Flujo
-
Lee el
facturascripts.inidel plugin y anotamin_version,min_phpyrequire. -
Localiza un clon git del core con todas sus etiquetas. Orden de búsqueda del script:
--core,FS_CORE_PATH,settings.corePathde~/.fs-claude.json, la raíz de la instalación cuando el plugin vive enPlugins/, y el directorio actual. Si no hay ninguno, pide clonarhttps://github.com/NeoRazorX/facturascripts.gity detente: sin historial no se puede datar ningún símbolo. -
Ejecuta el script de auditoría:
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/check-min-version.py" <ruta_plugin> --core <ruta_core> -
Lee completo el perfil
../../agents/compatibility-auditor.mdpara interpretar el informe y verificar a mano los símbolos de confianza media o baja. -
Ejecuta la auditoría de seguridad:
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/check-security.py" <ruta_plugin> -
Revisa en el código cada hallazgo de severidad alta o media siguiendo el apartado «Cómo revisar los hallazgos» del perfil, y clasifícalo como justificado, a vigilar o sospechoso.
-
Concluye con dos apartados:
- Compatibilidad: el
min_versioncorrecto, el símbolo concreto que lo determina y el archivo donde aparece. - Seguridad: los hallazgos revisados con su archivo, contexto de ejecución, destino y clasificación; los dominios externos; y lo que ha quedado sin revisar.
- Compatibilidad: el
Opciones de check-min-version.py
| Opción | Uso |
|---|---|
--json |
Informe completo para procesar símbolo a símbolo |
--include-tests |
Analiza también Test/, excluido por defecto |
--min-confidence alta |
Deja solo clases, llamadas estáticas, métodos con receptor tipado y pipes |
--plugins-dir |
Directorio Plugins/ para atribuir los símbolos de otros plugins |
--max-version X |
Incumple si el plugin usa algo retirado en la versión X del core o antes |
--workers N |
Ajusta las consultas simultáneas a git |
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.
- 10d ago Changed · +3 lines d263ed86d639
- 23d ago Changed · +33 lines · +13 tokens per session 87dea47d331d
- 24d ago First seen · 68 lines · 44 tokens per session scan A 083149675cb7
verificar-min-version is a skill published in the GitHub repository FacturaScripts/fs-claude-plugin (10 stars, last pushed 10d ago), licensed MIT. It adds 57 tokens to every session and 1,765 once invoked, about $0.0002 per session on Opus 5.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-09-23.
Other skills, from other repositories
sentry-php-sdk
Full Sentry SDK setup for PHP. Use when asked to "add Sentry to PHP", "install sentry/sentry", "setup Sentry in PHP", or configure error monitoring, tracing, profiling, logging, metrics, crons, or AI monitoring for PHP applications. Supports plain PHP, Laravel, and Symfony.
php-quality-tooling
Use when setting up PHPStan, Rector, or PHP-CS-Fixer on a non-Laravel PHP project, incl. CI wiring. Do NOT use for Laravel (Pint/Larastan), tests, or syntax.
wp-phpstan
Use when configuring, running, or fixing PHPStan static analysis in WordPress projects (plugins/themes/sites): phpstan.neon setup, baselines, WordPress-specific typing, and handling third-party plugin classes.
bug-root-cause-finder
Root cause analysis methods for PHP bugs. Provides 5 Whys technique, fault tree analysis, git bisect guidance, and stack trace parsing.
wp-phpstan-static-analysis
Run PHPStan static analysis on a WordPress plugin or theme using szepeviktor/phpstan-wordpress. Covers the composer dev-dependencies and what is pulled transitively (phpstan/phpstan ^2.0, php-stubs/wordpress-stubs), the optional phpstan/extension-installer that auto-registers the extension, the phpstan.neon.dist…
check-cascading-failures
Detects cascading failure risks in PHP systems. Identifies shared resources, unbounded queues, missing backpressure, thread pool exhaustion, and failure propagation paths.