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/bks-lab/open-bridge/schedulenpx skills add bks-lab/open-bridge --skill schedulegit clone --depth 1 https://github.com/bks-lab/open-bridgeWrote 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/bks-lab/open-bridge/schedule)<a href="https://agentmods.dev/skills/bks-lab/open-bridge/schedule"><img src="https://agentmods.dev/badge/skills/bks-lab/open-bridge/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.00069 | $0.00292 |
| Opus 5 | $0.00034 | $0.00146 |
| Sonnet 5 | $0.00014 | $0.00058 |
| Haiku 4.5 | $0.00007 | $0.00029 |
Grade A, and why
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 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.
What it actually says
Schedule
Manage scheduled tasks in infra/channels/_scheduled.yaml.
Read the referenced file ONLY when triggered.
Arguments
| Argument | Effect | Default |
|---|---|---|
list or (none) |
List scheduled tasks | — |
create |
Create new scheduled task | — |
deploy {name} |
Deploy to remote | — |
disable {name} |
Disable task | — |
status |
Show run status | — |
Decision Tree
User wants to...
├── List scheduled tasks → Read references/workflow.md (§ List)
├── Create new task → Read references/workflow.md (§ Create)
├── Deploy to remote → Read references/workflow.md (§ Deploy)
├── Disable a task → Read references/workflow.md (§ Disable)
├── Check status → Read references/workflow.md (§ Status)
└── Questions about scheduling → Answer from this file
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 39 lines · 69 tokens per session scan A 466088880e8e
schedule is a skill published in the GitHub repository bks-lab/open-bridge (8 stars, last pushed 4d ago), licensed MIT. It adds 69 tokens to every session and 292 once invoked, about $0.0003 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 skills, from other repositories
kungfu-agent-onboarding
Use when a user asks to understand, start, inspect, extend, or safely operate installed Kungfu; verify the installed pack, select one intent route, personalize the explanation, and propose one smallest safe next action.
with-frontmatter
Help an agent inspect a failed trace run, identify likely failure layers, and produce a short audit note.
minimal
Help an agent inspect a failed trace run, identify likely failure layers, and produce a short audit note.
beevibe-team-mesh-negotiation
Multi-round negotiation protocol — covers both initiator and peer roles. Use when about to call negotiate(), when receiving a intent block as a peer, or when receiving an 'escalated' sentinel from a blocked respondnegotiate. Covers proposal crafting, counter-strategy, deadlock detection, when to accept early…
beevibe-verify-pr
CI verification before marking a PR-bearing task done. Use BEFORE calling mcpbeevibeupdateprogress(done) on any session whose deliverable is a pull request — including the first dispatch (you opened the PR with gh pr create) and any revision dispatch (you pushed new commits to an existing PR). Watches the PR's…
beevibe-use-repo
You are the child agent inside a fresh Docker sandbox. Borrow the given GitHub repo, produce a real artifact for the goal, and export it. Do not review the repo. The proof is that it works.