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/smixs/agent-second-brain/cronnpx skills add smixs/agent-second-brain --skill crongit clone --depth 1 https://github.com/smixs/agent-second-brainWrote 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/smixs/agent-second-brain/cron)<a href="https://agentmods.dev/skills/smixs/agent-second-brain/cron"><img src="https://agentmods.dev/badge/skills/smixs/agent-second-brain/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.00068 | $0.01176 |
| Opus 5 | $0.00034 | $0.00588 |
| Sonnet 5 | $0.00014 | $0.00235 |
| Haiku 4.5 | $0.00007 | $0.00118 |
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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cron: расписания и напоминания
Ты управляешь своим расписанием сам — через CLI, который редактирует
jobs.json. Бот перечитывает файл каждую минуту и запускает задания в
отдельной cron-сессии. Результат запуска уходит пользователю в Telegram.
Команды
Рабочая директория — vault, проект уровнем выше (--project ..):
Таймзона. Время в
--cron— местное; ВСЕГДА передавай--tzзоной ПОЛЬЗОВАТЕЛЯ. Никогда не хардкодь чужую зону. В примерах ниже стоит"${TZ:-UTC}"— это РАБОЧЕЕ значение: shell подставит envTZ(зона из конфигурации пользователя), а если она не задана —UTC. Чтобы зафиксировать конкретную зону, замени на IANA-имя (напр.Europe/Moscow).<offset>в--at— UTC-смещение зоны (+05:00,+03:00,+00:00), его подставляешь при вычислении времени.
# Повторяющееся по cron-выражению (время местное — указывай --tz)
uv run --project .. python -m d_brain.cron add \
--prompt "Собери утреннюю сводку: вчерашний daily, goals недели" \
--cron "0 9 * * *" --tz "${TZ:-UTC}" --id morning-brief
# Интервал в секундах
uv run --project .. python -m d_brain.cron add \
--prompt "Проверь inbox в vault, новое разложи по карточкам. Если пусто — начни ответ с [SILENT]" \
--every 3600
# Разовое напоминание: ВСЕГДА --at + --delete-after-run
uv run --project .. python -m d_brain.cron add \
--prompt "Напомни про звонок с подрядчиком" \
--at "2026-06-12T18:00:00<offset>" --delete-after-run # <offset>, напр. +05:00
uv run --project .. python -m d_brain.cron list
uv run --project .. python -m d_brain.cron remove <id>
uv run --project .. python -m d_brain.cron enable <id> # вернуть авто-отключённый
Ошибка → exit 2 и текст в stderr: прочитай и исправь аргументы.
Перевод естественного языка в расписание
| Просьба | Аргументы |
|---|---|
| «каждый день в 9» | --cron "0 9 * * *" --tz "${TZ:-UTC}" |
| «по будням в 18:30» | --cron "30 18 * * 1-5" --tz "${TZ:-UTC}" |
| «каждое воскресенье» | --cron "0 10 * * 0" --tz "${TZ:-UTC}" |
| «каждый час» | --every 3600 |
| «каждые 15 минут» | --every 900 |
| «через 20 минут» | вычисли ISO-время: now+20m → --at <ISO> --delete-after-run |
| «завтра в 15» | --at "<завтра>T15:00:00<offset>" --delete-after-run |
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 · 76 lines · 68 tokens per session scan A 4e1fcbbc373d
cron is a skill published in the GitHub repository smixs/agent-second-brain (361 stars, last pushed 28d ago), licensed MIT. It adds 68 tokens to every session and 1,176 once invoked, about $0.0003 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-30.
Other skills, from other repositories
live-tutorial
Create an annotated MP4 tutorial from real screenshots of a workflow on the owner's computer. Use only when the owner explicitly asks for a tutorial video, not merely when they ask to watch an action happen live.
assimilate-popular-workflows
This skill should be used when the user asks to "find skills in the wild", "assimilate popular workflows", "discover SKILL.md files in repos", "research external skills", "find workflow patterns", "survey the skill landscape", "what skills exist out there", or wants to investigate public repositories for extractable…
process-builder
Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the 3-phase workflow from research to implementation.
retrospect-external-babysitter-run
For a repository in the babysitter-users catalog, locate its babysitter processes and any committed runs (.a5c/runs/ /) and perform a retrospective on a chosen run -- what went well, what failed, process suggestions, quality of effect design, breakpoint patterns -- mirroring the /babysitter:retrospect workflow but…
babysit
Orchestrate via @babysitter. Use this skill when asked to babysit a run, orchestrate a process or whenever it is called explicitly. (babysit, babysitter, orchestrate, orchestrate a run, workflow, etc.).
session-memory
Mandatory memory persistence system across session resets using three markdown surfaces in .claude/cc10x/. Iron law - every workflow must load at start and update at end.