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 zach-source/claude-mailbox --skill mailbox-leadergit clone --depth 1 https://github.com/zach-source/claude-mailboxWrote 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/zach-source/claude-mailbox/mailbox-leader)<a href="https://agentmods.dev/skills/zach-source/claude-mailbox/mailbox-leader"><img src="https://agentmods.dev/badge/skills/zach-source/claude-mailbox/mailbox-leader/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/zach-source/claude-mailbox/mailbox-leader"><img src="https://agentmods.dev/badge/skills/zach-source/claude-mailbox/mailbox-leader.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.00074 | $0.00442 |
| Opus 5 | $0.00037 | $0.00221 |
| Sonnet 5 | $0.00015 | $0.00088 |
| Haiku 4.5 | $0.00007 | $0.00044 |
Grade A, and why
mailbox-leader 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 9d 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
Mailbox leader / orchestrator
You are the leader when get_leader().leader_sid is your session (you're on
main). There is at most one leader; if you leave main, release leadership so
another main session can take over.
Responsibilities
- Know the field —
list_sessions()to see every active session, its project, worktree, branch, objective, and status. Stale sessions are marked; ignore them. - Delegate instead of doing everything —
delegate(to_sid, title, detail, priority)creates an assigned work item (amailbox:delegationbead) for a secondary. The open delegation beads ARE your ledger — query/track them rather than keeping state in your head. - Coordinate shared resources — serialize risky shared work (main merges,
flake.lock, deploys). Announce plans onbroadcast(text, channel="leader")so secondaries hold. - Answer requests — secondaries will
request_info/send_dmyou before shared actions;poll_inbox()and respond so they aren't blocked. - Hand off cleanly — if you switch off
main,release_leadership()(the heartbeat does this automatically when it detects you left main) and broadcast the handoff.
Failover
If the previous leader died, its slot goes stale and the next main session claims
it automatically at heartbeat. If leadership is vacant (nobody on main),
secondaries proceed autonomously but conservatively — you don't have to force a
claim unless the user wants a coordinator.
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.
- 9d ago First seen · 37 lines · 74 tokens per session scan A 0418b867d777
mailbox-leader is a skill published in the GitHub repository zach-source/claude-mailbox (1 stars, last pushed 1mo ago), licensed MIT. It adds 74 tokens to every session and 442 once invoked, about $0.0004 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.