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 commands/fiale-plus/fiale-claude-plugins/schedulegit clone --depth 1 https://github.com/fiale-plus/fiale-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/commands/fiale-plus/fiale-claude-plugins/schedule)<a href="https://agentmods.dev/commands/fiale-plus/fiale-claude-plugins/schedule"><img src="https://agentmods.dev/badge/commands/fiale-plus/fiale-claude-plugins/schedule.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.00020 | $0.01389 |
| Opus 5 | $0.00010 | $0.00694 |
| Sonnet 5 | $0.00004 | $0.00278 |
| Haiku 4.5 | $0.00002 | $0.00139 |
Grade A, and why
brain-schedule 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 3d 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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Manage automated scheduling for /synthesize and /brain-reflect. Safe to re-run — checks before adding duplicates.
Usage
Run with one of:
/brain-schedule— interactive: shows current state, asks what to install/remove/brain-schedule install synthesize— install synthesize job only/brain-schedule install reflect— install reflect job only/brain-schedule install all— install both/brain-schedule remove synthesize— remove synthesize job/brain-schedule remove reflect— remove reflect job/brain-schedule remove all— remove all brain jobs/brain-schedule status— show current installed jobs
Steps
1. Detect OS and existing jobs
uname -s
which claude
Check current crontab:
crontab -l 2>/dev/null | grep -n "brain:\|/synthesize\|/brain-reflect" || echo "none"
On macOS, also check launchd:
ls ~/Library/LaunchAgents/com.brain.*.plist 2>/dev/null || echo "none"
2. If interactive (no arguments), show status and ask
Current brain schedule:
synthesize: <installed at 09:00 daily via cron | not installed>
reflect: <installed at 09:00 Mondays via cron | not installed>
What would you like to do?
1. Install synthesize (daily)
2. Install reflect (weekly, Mondays)
3. Install both
4. Remove synthesize
5. Remove reflect
6. Remove all
7. Change schedule time
8. Exit
3. Ask scheduler preference (if installing, macOS only)
On macOS, ask:
"Use launchd (recommended — runs even without a terminal) or cron?"
- launchd
- cron
On Linux, use cron only.
4. Ask for schedule time (if installing)
"What time should synthesis run? Default is 09:00. Enter as HH:MM or press Enter."
Parse into hour and minute. For reflect, ask day of week (default: Monday).
5. Install jobs
CLAUDE_PATH = output of which claude
HOME_DIR = output of echo $HOME
LOG = ~/.claude/brain/cron.log
cron — install synthesize
Check if already present:
crontab -l 2>/dev/null | grep "/synthesize"
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.
- 3d ago First seen · 180 lines · 20 tokens per session scan A ef86abf5f69d
brain-schedule is a command published in the GitHub repository fiale-plus/fiale-claude-plugins (4 stars, last pushed 4mo ago), licensed MIT. It adds 20 tokens to every session and 1,389 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 commands, from other repositories
statusbar-reset
Wipe the status-bar config back to defaults.
self-healing
Automatically detect and recover from errors without interrupting your flow.
session-memory
Maintain context and learnings across Claude Code sessions for continuous improvement.
statusbar-style
Switch the status-bar style (classic / capsule / hairline).
kingfisher
Find, live-validate, map the blast radius of, and revoke leaked secrets with Kingfisher (MongoDB) — across a local repo, Git history, a GitHub/GitLab/Bitbucket org, S3/GCS, Docker images, Slack, Jira, Confluence, Teams, or Postman. Covers local CLI scanning, direct validate/revoke without a scan, baseline management…
apollo-migrate
Migrate the Apollo repository $ARGUMENTS to the new GraphQLClientProtocol pattern.