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 skills add martineserios/thebrana --skill schedulergit clone --depth 1 https://github.com/martineserios/thebranaWrote 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/martineserios/thebrana/scheduler)<a href="https://agentmods.dev/skills/martineserios/thebrana/scheduler"><img src="https://agentmods.dev/badge/skills/martineserios/thebrana/scheduler/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/skills/martineserios/thebrana/scheduler"><img src="https://agentmods.dev/badge/skills/martineserios/thebrana/scheduler.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.00033 | $0.00686 |
| Opus 5 | $0.00016 | $0.00343 |
| Sonnet 5 | $0.00007 | $0.00137 |
| Haiku 4.5 | $0.00003 | $0.00069 |
Grade A, and why
scheduler 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.
What it actually says
Scheduler Management
Manage scheduled brana jobs from within Claude Code. This skill wraps the brana-scheduler CLI.
Available commands
Run these via Bash tool:
| Action | Command |
|---|---|
| Show all jobs | brana-scheduler status |
| Show job logs | brana-scheduler logs <job-name> |
| Show last N runs | brana-scheduler logs <job-name> -n 5 |
| Enable a job | brana-scheduler enable <job-name> |
| Disable a job | brana-scheduler disable <job-name> |
| Run a job now | brana-scheduler run <job-name> |
| Validate config | brana-scheduler validate |
| Redeploy after config changes | brana-scheduler deploy |
| Remove all timers | brana-scheduler teardown |
When invoked
- Run
brana-scheduler statusto show current state - Ask the user what they want to do (view logs, toggle jobs, run something)
- Execute the appropriate command
Adding a new job
Guide the user to edit ~/.claude/scheduler/scheduler.json:
"my-new-job": {
"type": "skill",
"skill": "/skill-name",
"project": "~/path/to/project",
"schedule": "Mon *-*-* 09:00:00",
"model": "haiku",
"enabled": true
}
After editing, run brana-scheduler deploy to activate.
Schedule syntax (systemd OnCalendar)
| Pattern | Meaning |
|---|---|
Mon *-*-* 09:00:00 |
Every Monday at 9am |
Mon..Fri *-*-* 08:00:00 |
Weekdays at 8am |
Fri *-*-* 17:00:00 |
Every Friday at 5pm |
*-*-01 10:00:00 |
1st of every month at 10am |
*-*-* 06:00:00 |
Daily at 6am |
Test with: systemd-analyze calendar "Mon *-*-* 09:00:00"
Job types
"type": "skill"— runsclaude -p "Execute the /skill-name skill"in the project directory"type": "command"— runs a shell command directly in the project directory
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 · 77 lines · 33 tokens per session scan A 7b8484d1b495
scheduler is a skill published in the GitHub repository martineserios/thebrana (3 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 686 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-09-03.
Other skills, from other repositories
cron-scheduler
Schedule and manage automated tasks with cron expressions - create recurring jobs, one-time tasks, natural language scheduling, and cross-platform timer management.
scaffold
Bootstrap a new project with your stack, auth, database, and standards pre-configured.
status
A progress-reporting command that reads phase logs from a project and displays a summary in English or Korean.
pr-review-watcher
Monitors for incoming PR reviews and summarizes their content. Determines approval/change-request/comment verdicts and extracts action items. Triggers on "did the PR review come in?", "when will the review arrive", "PR waiting" utterances.
tasks
A task-breakdown tool that turns a plan, specification, feature brief, bug report, technical-debt item, or chore into small TASK-NNN work items. Technical debt means postponed cleanup or design work in a codebase.
continue
Autonomous work — find and execute ready tasks.