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/onebrain-ai/onebrain/schedule-addnpx skills add onebrain-ai/onebrain --skill schedule-addgit clone --depth 1 https://github.com/onebrain-ai/onebrainWrote 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/onebrain-ai/onebrain/schedule-add)<a href="https://agentmods.dev/skills/onebrain-ai/onebrain/schedule-add"><img src="https://agentmods.dev/badge/skills/onebrain-ai/onebrain/schedule-add.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.00037 | $0.02406 |
| Opus 5 | $0.00018 | $0.01203 |
| Sonnet 5 | $0.00007 | $0.00481 |
| Haiku 4.5 | $0.00004 | $0.00241 |
Grade A, and why
schedule-add 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 — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/schedule-add — Interactive scheduler wizard
Purpose
For users who don't want to hand-edit onebrain.yml or learn cron syntax. Walks through:
- Which skill to schedule
- How often (Daily/Weekly/Monthly/Custom)
- What time
- Confirms cron preview
- Writes to onebrain.yml + runs
onebrain schedule register
Skill flow
Step 0: First-run preset detection (skip if schedule already has entries)
-
Read
onebrain.yml. Check if theschedule:key exists AND its value is a non-empty list.- If
schedule:is missing, null, or[]→ continue with this step (preset selector). - If
schedule:has one or more entries → skip Step 0 entirely; go straight to Step 1.
- If
-
Read the canonical preset tier table from
.claude/plugins/onebrain/skills/_shared/schedule-presets.md. The four tiers are defined there — never duplicate them inline in this skill file. -
Show preset selection via
AskUserQuestion:- Tier 1 — Minimal (1 entry:
/daily09:00 every day) - Tier 2 — Essentials (Recommended) (3 entries:
/daily,/weeklyFriday,/recapSunday) - Tier 3 — Maintenance Plus (6 entries: Essentials +
/doctormonthly +/tasksdaily +onebrain search reindexSunday command-mode entry) - Tier 4 — Custom (skip presets, go to manual wizard)
- Tier 1 — Minimal (1 entry:
-
Apply the chosen tier:
- Tier 1, 2, or 3: atomically write the preset entries (verbatim from
_shared/schedule-presets.md) toonebrain.ymlschedule:block (load → mutate → write entire file; use a tmp file + rename). Then runonebrain schedule register. Confirm:✓ Installed Tier N preset (M entries). - Tier 4 (Custom): fall through to Step 1 (the existing skill picker wizard).
- Tier 1, 2, or 3: atomically write the preset entries (verbatim from
-
On Tier 1/2/3 success → the skill exits here. The user has scheduled entries. Subsequent invocations of
/schedule-addwill seeschedule:is non-empty and skip Step 0, falling straight into the manual wizard for adding additional entries.
Edge cases
- onebrain.yml missing entirely → wizard creates it with the preset entries as the only content of a new
schedule:block. - onebrain.yml has
schedule:as a comment or YAML null → treat as empty; proceed with preset selector. - Atomic write failure → rollback (do not leave partial state); report the YAML error and exit.
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 First seen · 220 lines · 37 tokens per session scan A 4b23ac9f190f
schedule-add is a skill published in the GitHub repository onebrain-ai/onebrain (26 stars, last pushed 8d ago), licensed Apache-2.0. It adds 37 tokens to every session and 2,406 once invoked, about $0.0002 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
obsidian-cli
Interact with Obsidian vaults using the Obsidian CLI to read, create, search, and manage notes, tasks, properties, and more. Also supports plugin and theme development with commands to reload plugins, run JavaScript, capture errors, take screenshots, and inspect the DOM. Use when the user asks to interact with their…
priority-dashboard
Use this to rebuild, inspect, or temporarily steer {{username}}'s current PersonalOS priority dashboard from canonical Actions, Attention Triggers, and owner context. Do NOT use it to create, complete, or independently manage tasks; use task-manager for Action and Trigger lifecycle changes.
wrap-session-up
End-of-session review for a Claude Code conversation. Replays what was discussed, checks for open action items, documents relevant outcomes in the brain vault, and creates Todoist tasks for anything untracked. Use at the end of a work session to ensure nothing falls through the cracks.
task-manager
Use this when {{username}} or an agent wants to add, review, prioritize, complete, defer, park, or inspect todos, open loops, confirmed actions, waiting states, or attention triggers. Maintains atomic records under operations/actions/ and operations/attention-triggers/ as the only local action truth. Do NOT use for…
gws-obsidian-prep
Cross-skill recipe: fetch today's (or tomorrow's) Google Calendar events via gws CLI and create meeting prep notes in the Obsidian vault.
resume
Восстановление контекста припаркованной задачи для продолжения работы. Агент сканирует plan.md §Blockers, log.md и delegations/-файлы активных проектов, находит активные блокеры, записи PAUSED и открытые делегирования, показывает пользователю список припаркованных задач с типами и триггерами, и после выбора загружает…