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 vmkteam/claude-plugins --skill crongit clone --depth 1 https://github.com/vmkteam/claude-pluginsWrote 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/vmkteam/claude-plugins/cron)<a href="https://agentmods.dev/skills/vmkteam/claude-plugins/cron"><img src="https://agentmods.dev/badge/skills/vmkteam/claude-plugins/cron/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/vmkteam/claude-plugins/cron"><img src="https://agentmods.dev/badge/skills/vmkteam/claude-plugins/cron.svg" alt="Reviewed on agentmods" width="80" 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.00071 | $0.01062 |
| Opus 5.5 | $0.00028 | $0.00425 |
| Sonnet 5.5 | $0.00014 | $0.00212 |
| Haiku 4.5 | $0.00007 | $0.00106 |
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 6d 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cron
- Upstream: https://github.com/vmkteam/cron
- Обёртка над robfig/cron: context-aware jobs, web UI, ручной запуск, middleware, метрики
- Сигнатура задачи:
func(ctx context.Context) error
Воркеры не живут в пакете домена. Расписание — pkg/app/cron.go (newCron(), CronConfig), задача — метод менеджера домена func(ctx) error. Пакет <domain>/cron и свой генерик Job поверх vmkteam/cron не нужны: менеджер уже даёт DI, middleware — метрики, логи и Sentry.
Базовый шаблон
m := cron.NewManager()
m.Use(
cron.WithMetrics("mysrv"),
cron.WithDevel(cfg.IsDevel),
cron.WithSLog(logger),
cron.WithMaintenance(log.Printf),
cron.WithSkipActive(),
cron.WithRecover(),
cron.WithSentry(),
)
m.AddFunc("sync-users", "*/5 * * * *", func(ctx context.Context) error { ... })
m.AddMaintenanceFunc("db-vacuum", "0 4 * * 0", ...) // эксклюзивный, блокирует остальные
m.AddFunc("manual-import", "", ...) // "" = только ручной запуск
go m.Run(ctx)
http.HandleFunc("/debug/cron", m.Handler)
Middleware
| MW | Назначение |
|---|---|
WithMetrics(serverName) |
Prometheus (count/duration/active) |
WithSLog(logger) |
structured logging |
WithLogger(printf, serverName) |
legacy Printf |
WithSentry() |
ошибки + panic recovery → Sentry |
WithRecover() |
panic recovery (альтернатива WithSentry) |
WithDevel(isDevel) |
dev-флаг в ctx |
WithSkipActive() |
обязателен для длинных задач — пропуск если предыдущий запуск ещё идёт |
WithMaintenance(printf) |
эксклюзивное выполнение maintenance-задач |
Метрики
app_cron_evaluated_total— counter выполнений по состояниямapp_cron_active— gauge активных задачapp_cron_evaluated_duration_seconds— summary длительности
UI / API
GET /debug/cron— HTML расписание (имя, паттерн, next, state, duration)GET /debug/cronсAccept: application/json— JSONGET /debug/cron?start=<name>— ручной запуск (follow redirect)
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.
- 6d ago Changed · +2 lines · +21 tokens per session 1de16407ea55
- 1mo ago First seen · 107 lines · 50 tokens per session scan A f75728b422cb
cron is a skill published in the GitHub repository vmkteam/claude-plugins (7 stars, last pushed 6d ago), licensed MIT. It adds 71 tokens to every session and 1,062 once invoked, about $0.0003 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
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…