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 agentmods add skills/facturascripts/fs-claude-plugin/crear-pluginnpx skills add FacturaScripts/fs-claude-plugin --skill crear-plugingit 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/crear-plugin)<a href="https://agentmods.dev/skills/facturascripts/fs-claude-plugin/crear-plugin"><img src="https://agentmods.dev/badge/skills/facturascripts/fs-claude-plugin/crear-plugin.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 | $0.00022 | $0.00582 |
| Opus 5 | $0.00011 | $0.00291 |
| Sonnet 5 | $0.00004 | $0.00116 |
| Haiku 4.5 | $0.00002 | $0.00058 |
Grade A, and why
crear-plugin 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 4d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Crear Plugin FacturaScripts
Cuando el usuario pida crear un nuevo plugin para FacturaScripts, sigue estos pasos:
Atajo con fsmaker
Antes de crear los archivos a mano, considera usar la herramienta CLI:
fsmaker plugin
fsmaker solicita el nombre, descripción y versión mínima, y genera toda la estructura de carpetas y archivos automáticamente. Los pasos siguientes explican la estructura y el contenido en detalle para cuando necesites crearlos o modificarlos manualmente.
Paso 1: Obtener información del plugin
Pregunta al usuario:
- Nombre del plugin (sin espacios, empieza por mayúscula. Ej:
MiPlugin) - Descripción breve
- Versión mínima de FacturaScripts (por defecto: 2025)
Paso 2: Crear la estructura de carpetas
Crea la siguiente estructura en Plugins/NombrePlugin/:
Plugins/NombrePlugin/
├── Assets/
│ ├── CSS/
│ ├── Images/
│ └── JS/
├── Controller/
├── Extension/
│ ├── Controller/
│ ├── Model/
│ └── View/
├── Model/
├── Table/
├── Translation/
├── View/
├── XMLView/
├── facturascripts.ini
└── Init.php
Paso 3: Crear facturascripts.ini
name = 'NombrePlugin'
description = 'Descripción del plugin'
version = 1
min_version = 2025
Paso 4: Crear Init.php
<?php
namespace FacturaScripts\Plugins\NombrePlugin;
use FacturaScripts\Core\Template\InitClass;
class Init extends InitClass
{
public function init(): void
{
// Cargar extensiones aquí
// $this->loadExtension(new Extension\Model\MiModelo());
}
public function uninstall(): void
{
// Limpieza al desinstalar
}
public function update(): void
{
// Cambios al instalar/actualizar
}
}
Reglas importantes
- El nombre del plugin NO puede empezar por número ni contener espacios
- El namespace siempre es
FacturaScripts\Plugins\NombrePlugin - Nunca modificar archivos de
Core/niDinamic/ - Activar el plugin desde Administrador → Plugins tras crearlo
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.
- 4d ago First seen · 99 lines · 22 tokens per session scan A 202e696009e7
crear-plugin is a skill published in the GitHub repository FacturaScripts/fs-claude-plugin (8 stars, last pushed 2mo ago), licensed MIT. It adds 22 tokens to every session and 582 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…