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/skill-noticenpx skills add FacturaScripts/fs-claude-plugin --skill skill-noticegit 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-notice)<a href="https://agentmods.dev/skills/facturascripts/fs-claude-plugin/skill-notice"><img src="https://agentmods.dev/badge/skills/facturascripts/fs-claude-plugin/skill-notice.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.1 | $0.00145 | $0.01432 |
| Opus 5 | $0.00072 | $0.00716 |
| Sonnet 5 | $0.00029 | $0.00286 |
| Haiku 4.5 | $0.00015 | $0.00143 |
Grade A, and why
skill-notice 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 5d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Noticia de cambios (changelog) — Buenas prácticas
El objetivo de esta skill es redactar un texto claro y atractivo que comunique a usuarios y clientes qué hay de nuevo en una versión: nuevas funcionalidades, mejoras y correcciones de errores. El texto está pensado para publicarse (en la forja de FacturaScripts, en un changelog, en una nota de lanzamiento o en redes), por lo que debe ser comprensible para quien usa el ERP, no solo para quien programa.
Reglas fundamentales
- No crees ningún archivo. El resultado se muestra directamente en el chat, dentro de un bloque de código markdown, para que el usuario lo copie y lo pegue donde quiera. Nunca escribas el texto en un fichero del proyecto salvo que el usuario lo pida explícitamente.
- Acota el rango. El usuario indicará el alcance de los cambios, normalmente de una de estas
formas:
- Por versiones: "desde la versión 1.1.0 hasta la 1.2.0".
- Por commits: "desde el commit
abc123hastaHEAD". - Por referencia temporal: "los cambios de la última semana", "desde el último release". Si no indica rango, pregúntale desde qué versión/commit hasta cuál quiere la noticia.
- Redacta orientado al usuario, no al desarrollador. Traduce los cambios técnicos a beneficios y comportamientos visibles. Por ejemplo, en lugar de "refactor del Calculator", escribe "los totales de las facturas ahora se recalculan correctamente al cambiar la serie".
Flujo de trabajo
Cuando el usuario pida la noticia de cambios, sigue este orden:
- Determina el rango de commits. Según lo que indique el usuario:
- Entre dos versiones (si están etiquetadas como tags de git):
git log v1.1.0..v1.2.0 --pretty=format:"%h %s" --no-merges - Entre dos commits:
git log abc123..def456 --pretty=format:"%h %s" --no-merges - Desde el último tag hasta ahora:
git log $(git describe --tags --abbrev=0)..HEAD --pretty=format:"%h %s" --no-merges - Por fecha:
git log --since="2026-06-01" --pretty=format:"%h %s" --no-merges
- Entre dos versiones (si están etiquetadas como tags de 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.
- 5d ago First seen · 114 lines · 145 tokens per session scan A 9e6325e2c30d
skill-notice is a skill published in the GitHub repository FacturaScripts/fs-claude-plugin (8 stars, last pushed 3d ago), licensed MIT. It adds 145 tokens to every session and 1,432 once invoked, about $0.0007 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…