crear-plugin

crear-plugin is a skill for Claude Code, Codex from FacturaScripts/fs-claude-plugin. It costs 22 tokens per session (582 once invoked), scanned A, original, MIT.

A Spanish-language guide for creating a FacturaScripts plugin, including its folders and required files. FacturaScripts is business software that can be extended with plugins.

In plain words
What is it for?
Use it to gather the plugin name, description, and minimum software version, then generate or create the standard folders, controllers, models, views, translations, assets, and initialization files.
Why use it?
It avoids having to remember the plugin layout and the setup steps needed for a new extension.

Skill for Claude CodeCodex

Part of the fs-dev plugin — 28 skills, 11 agents, 3 hooks shipped together

Install

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.

agentmods
npx agentmods add skills/facturascripts/fs-claude-plugin/crear-plugin
Any agent
npx skills add FacturaScripts/fs-claude-plugin --skill crear-plugin
Clone the repo
git clone --depth 1 https://github.com/FacturaScripts/fs-claude-plugin

Made for: Claude Code, Codex.

Or install fs-dev, the plugin that ships this one along with the rest of its 28 skills, 11 agents, 3 hooks.

Wrote 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.

agentmods badge for crear-plugin

README.md
[![agentmods](https://agentmods.dev/badge/skills/facturascripts/fs-claude-plugin/crear-plugin.svg)](https://agentmods.dev/skills/facturascripts/fs-claude-plugin/crear-plugin)
Your own site
<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>
Per session 22 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 582 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 4d ago against content hash 202e696009e7, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

fs-dev/skills/crear-plugin/SKILL.md · 99 lines

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/ ni Dinamic/
  • Activar el plugin desde Administrador → Plugins tras crearlo

Read the full file on GitHub · 99 lines

Changes

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.

  1. 4d ago First seen · 99 lines · 22 tokens per session scan A 202e696009e7

Subscribe to this mod's changes

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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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.

obra/superpowers · 37 tokens

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.

microsoft/vscode · 62 tokens

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.

microsoft/vscode · 51 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens