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/cronnpx skills add FacturaScripts/fs-claude-plugin --skill crongit 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/cron)<a href="https://agentmods.dev/skills/facturascripts/fs-claude-plugin/cron"><img src="https://agentmods.dev/badge/skills/facturascripts/fs-claude-plugin/cron.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.00029 | $0.01091 |
| Opus 5 | $0.00015 | $0.00545 |
| Sonnet 5 | $0.00006 | $0.00218 |
| Haiku 4.5 | $0.00003 | $0.00109 |
Grade A, and why
cron 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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Cron — Tareas Periódicas en FacturaScripts
El sistema de cron de FacturaScripts permite ejecutar tareas periódicas en los plugins. Cada plugin puede tener su propio archivo Cron.php que hereda de CronClass. El cron del sistema gestionará automáticamente todos los procesos cron de los plugins activos.
Requisito previo
El cron del sistema debe estar configurado correctamente en el servidor o hosting para que se ejecute periódicamente (por ejemplo, cada minuto).
Atajo con fsmaker
Para generar automáticamente el archivo Cron.php y añadir un nuevo CronJob:
# Crear el archivo Cron.php base del plugin
fsmaker cron
# Crear un nuevo CronJob y registrarlo en Cron.php
fsmaker cronjob
Estructura básica de Cron.php
<?php
namespace FacturaScripts\Plugins\MiPlugin;
use FacturaScripts\Core\Template\CronClass;
class Cron extends CronClass
{
public function run(): void
{
// tu código aquí
}
}
Todo el código dentro de run() se ejecutará cada vez que se active el cron. Para controlar la frecuencia de ejecución de trabajos individuales, se usa el método job().
Frecuencias de ejecución
Cada X horas o días
public function run(): void
{
// ejecutar cada hora
$this->job('mi-trabajo')
->every('1 hour')
->run(function () {
// código a ejecutar cada hora
});
// ejecutar cada 6 horas
$this->job('otro-trabajo')
->every('6 hours')
->run(function () {
// código a ejecutar cada 6 horas
});
// ejecutar cada 10 días
$this->job('trabajo-dias')
->every('10 days')
->run(function () {
// código a ejecutar cada 10 días
});
}
Cada día a una hora concreta
$this->job('mi-trabajo')
->everyDayAt(8)
->run(function () {
// se ejecutará cada día a las 8h
});
Si necesitas una comprobación más estricta (solo ejecutar exactamente a esa hora, sin recuperar ejecuciones perdidas):
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 · 178 lines · 29 tokens per session scan A 0726e9d477c3
cron is a skill published in the GitHub repository FacturaScripts/fs-claude-plugin (8 stars, last pushed 2mo ago), licensed MIT. It adds 29 tokens to every session and 1,091 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…