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-removenpx skills add onebrain-ai/onebrain --skill schedule-removegit 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-remove)<a href="https://agentmods.dev/skills/onebrain-ai/onebrain/schedule-remove"><img src="https://agentmods.dev/badge/skills/onebrain-ai/onebrain/schedule-remove.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.00025 | $0.00696 |
| Opus 5 | $0.00013 | $0.00348 |
| Sonnet 5 | $0.00005 | $0.00139 |
| Haiku 4.5 | $0.00003 | $0.00070 |
Grade A, and why
schedule-remove 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/schedule-remove — Remove a scheduled skill
Purpose
Safely unschedule a skill: presents the current schedule, confirms intent, removes the entry from onebrain.yml, and unregisters the corresponding launchd job.
Skill flow
Step 1: Show current schedule
Run the /schedule-list logic (read onebrain.yml schedule: block + call onebrain schedule register --status) to display the current entries.
If no entries are found:
No scheduled skills to remove.
→ Run /schedule-add to set one up.
Stop.
Step 2: Pick entry to remove
Show via AskUserQuestion:
- question: "Which scheduled skill would you like to remove?"
- header: "Remove Schedule"
- multiSelect: false
- options: one option per scheduled entry, label =
/skill-namewith cron and frequency as description- e.g. label:
/daily, description:0 9 * * * — daily at 09:00
- e.g. label:
Store: chosen_entry (the matched onebrain.yml schedule entry).
Step 3: Confirm removal
Show via AskUserQuestion:
- question: "Remove
{chosen_skill}scheduled at{cron}({frequency_description})? This stops all automatic invocations." - header: "Confirm Removal"
- multiSelect: false
- options:
- label: "Yes, remove it", description: "Delete the schedule entry and unregister it from the OS scheduler"
- label: "Cancel", description: "Keep the schedule as-is"
If Cancel, stop.
Step 4: Edit onebrain.yml
Read onebrain.yml. Remove the matching entry from the schedule: block.
Write the full updated onebrain.yml back atomically:
- Write to
onebrain.yml.tmpin the vault root. - Rename to
onebrain.yml.
If the write fails, delete onebrain.yml.tmp if it exists and report the error. Do not proceed to Step 5.
Step 5: Unregister
Run from the vault root:
onebrain schedule register --refresh
This re-reads onebrain.yml (now without the removed entry) and deactivates + deletes the corresponding OS scheduler artifact (launchd plist · Scheduled Task · systemd user units).
If the command fails, report the error. onebrain.yml has already been updated — the user can retry onebrain schedule register --refresh manually.
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 · 89 lines · 25 tokens per session scan A f7f5bf157cc4
schedule-remove is a skill published in the GitHub repository onebrain-ai/onebrain (25 stars, last pushed 6d ago), licensed Apache-2.0. It adds 25 tokens to every session and 696 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-30.
Other skills, from other repositories
excalidraw-diagram
Generate Excalidraw diagrams from text content. Supports three output modes - Obsidian (.md), Standard (.excalidraw), and Animated (.excalidraw with animation order). Triggers on "Excalidraw", "diagram", "standard excalidraw", "animate".
mermaid-visualizer
Transform text content into professional Mermaid diagrams for presentations and documentation. Use when users ask to visualize concepts, create flowcharts, or make diagrams from text. Supports process flows, system architectures, comparisons, mindmaps, and more with built-in syntax error prevention.
qmd
Search the vault using QMD semantic search. Use PROACTIVELY before reading files. Preference order: (1) MCP tools — mcpqmdquery, mcpqmdget, mcpqmdmultiget, mcpqmdstatus — if they appear in your tool menu, use them first; (2) CLI qmd --index ... as fallback; (3) Grep/Glob only when QMD is not installed. Trigger…
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…
deeppapernote
Generate a high-quality deep-reading note for a single paper and write it into an Obsidian-style vault. Use when the user gives a paper title, DOI, URL, arXiv ID, Zotero item, or local PDF and wants a polished Markdown note with strong structure, evidence-based analysis, and figure placeholders.
paper-glossary
Use when building reusable Obsidian glossary notes from an existing paper source manifest, optionally with a raw-sections override, especially when a reader needs a reviewed shortlist before glossary notes and article links are changed.