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 skill-commitgit 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/skill-commit)<a href="https://agentmods.dev/skills/facturascripts/fs-claude-plugin/skill-commit"><img src="https://agentmods.dev/badge/skills/facturascripts/fs-claude-plugin/skill-commit/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/skill-commit"><img src="https://agentmods.dev/badge/skills/facturascripts/fs-claude-plugin/skill-commit.svg" alt="Reviewed on agentmods" width="80" 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.00033 | $0.01278 |
| Opus 5.5 | $0.00013 | $0.00511 |
| Sonnet 5.5 | $0.00007 | $0.00256 |
| Haiku 4.5 | $0.00003 | $0.00128 |
Grade A, and why
skill-commit 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 1mo 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commits en Git — Buenas Prácticas
El objetivo de un buen commit es que cualquier persona del equipo (o tú mismo dentro de 6 meses) pueda entender qué se cambió y por qué con solo leer el historial de git. Un commit bien hecho facilita las revisiones de código, simplifica los reverts y hace que el proyecto sea más mantenible.
Estructura del mensaje de commit
Usa el formato de Conventional Commits adaptado al español:
<tipo>(<ámbito>): <descripción breve>
<cuerpo opcional>
<pie opcional>
Ejemplo 1:
feat(facturas): añadir campo de descuento por pronto pago
Se añade un nuevo campo en el modelo de factura que permite
aplicar un porcentaje de descuento cuando el cliente paga
antes de la fecha de vencimiento.
Ejemplo 2:
fix(informes): corregir cálculo de IVA en informe trimestral
El IVA se estaba calculando sobre el total con descuento en
lugar de sobre la base imponible. Ahora se aplica correctamente.
Ejemplo 3 (simple):
docs(readme): actualizar instrucciones de instalación
Código de tarea en el commit
Cuando el usuario proporcione un código de tarea (por ejemplo, un número de issue o tarea del roadmap como 4543, #1234, TASK-567, etc.), este código debe incluirse en el título del commit, justo después del tipo (y ámbito si lo hay), antes de la descripción. Solo se incluye el código numérico o identificador, sin enlaces ni texto adicional.
Formato con código de tarea:
<tipo>: <código> <descripción breve>
Formato con código de tarea y ámbito:
<tipo>(<ámbito>): <código> <descripción breve>
Ejemplos con código de tarea:
feat: 4543 añadir filtro por fecha de pago en las listas de anticipos de clientes y proveedores
fix: 1287 corregir cálculo de IVA en informe trimestral
feat(facturas): 3201 añadir campo de descuento por pronto pago
Si el usuario no menciona ningún código de tarea, el commit se escribe sin él, siguiendo el formato estándar.
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.
- 1mo ago Changed · -4 lines · -59 tokens per session 17a6ca9059a4
- 1mo ago First seen · 134 lines · 92 tokens per session scan A d681cb761ec6
skill-commit is a skill published in the GitHub repository FacturaScripts/fs-claude-plugin (10 stars, last pushed 10d ago), licensed MIT. It adds 33 tokens to every session and 1,278 once invoked, about $0.0001 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-08-31.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
repo-sync
Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…
git-commit-writer
Trigger when the user asks to write a commit message, generate a commit from staged changes, review a diff before committing, or says "/commit". Reads git diff --staged and produces an opinionated, convention-matching commit message.