Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Bitmia-ai/RedEyenpx agentmods add commands/bitmia-ai/redeye/schedulesWrote 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/bitmia-ai/redeye/schedules)<a href="https://agentmods.dev/commands/bitmia-ai/redeye/schedules"><img src="https://agentmods.dev/badge/commands/bitmia-ai/redeye/schedules/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/commands/bitmia-ai/redeye/schedules"><img src="https://agentmods.dev/badge/commands/bitmia-ai/redeye/schedules.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.00004 | $0.00356 |
| Opus 5.5 | $0.00002 | $0.00142 |
| Sonnet 5.5 | $0.00001 | $0.00071 |
| Haiku 4.5 | $0.00000 | $0.00036 |
Grade A, and why
schedules 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 1mo 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.
What it actually says
Read .redeye/schedules.md from the project root.
Show current schedules: List all SCHED-{id} entries with title, frequency, and last run time.
Offer interactive management via AskUserQuestion:
- Add new schedule — ask for: title, frequency, steps, assigned role(s). Then create the entry via
scripts/create-schedule.sh(the ONLY supported path for creating schedules — it enforces the 1-hour floor, validates the frequency syntaxevery <N><h|d|w>, atomically allocates the next SCHED-NNN ID fromstate.json.counters.next_sched_id, and inserts the entry at the end of the file):
Do NOT hand-authorbash scripts/create-schedule.sh \ --title "<title>" \ --frequency "every <N><h|d|w>" \ --task-step "<step 1>" \ --task-step "<step 2>" \ [--assigned-to "<roles>"] \ [--last-run "<ISO timestamp>"]### SCHED-NNN:blocks — malformed entries (bad frequency, missing fields) are silently skipped by the dashboard's overdue-detection. - Edit schedule — hand-editing existing fields (frequency, steps, assigned-to, last-run) is fine; do not create new entries this way.
- Remove schedule — delete the entire
### SCHED-NNN:block. - Done — exit.
After any changes:
git add .redeye/schedules.md .redeye/state.json
git commit -m "redeye: update schedules"
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.
- 1mo ago First seen · 32 lines · 4 tokens per session scan A 8538be2f436d
schedules is a command published in the GitHub repository Bitmia-ai/RedEye (6 stars, last pushed 4mo ago), licensed MIT. It adds 4 tokens to every session and 356 once invoked, about $0.0000 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 commands, from other repositories
scout-meta-review
Run an interactive Scout meta-review — a system-level audit that sits above the individual session types. Checks whether sessions are running, mistake audit is trending well, proposals are flowing, KB files are healthy, and data-source coverage is consistent across session types. Runs in the current conversation.
scout-work
Interactive work session — walks through today's actionable items one at a time, presents a recommended action with draft content, and executes each one only with explicit approval. Runs in the current conversation (not as a background session).
resume
Resume an interrupted multi-phase orc command from its last checkpoint. Reads .orc/orc.json for active sessions, picks one, jumps to the next pending phase. Workspace-aware.
retro
Retrospective on a coding session — proposes changes to the agent's environment (navigation pointers, automated checks, coding standards, steering files, tool economy, information access), most severe first; applies accepted in-repo changes and files the rest through the tracker gate.
inbox
Check beadle's email inbox.
contacts
Manage your address book.