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/thrashr888/allbeads/mailgit clone --depth 1 https://github.com/thrashr888/AllBeadsWrote 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/thrashr888/allbeads/mail)<a href="https://agentmods.dev/commands/thrashr888/allbeads/mail"><img src="https://agentmods.dev/badge/commands/thrashr888/allbeads/mail.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.1 | $0.00008 | $0.00935 |
| Opus 5 | $0.00004 | $0.00467 |
| Sonnet 5 | $0.00002 | $0.00187 |
| Haiku 4.5 | $0.00001 | $0.00093 |
Grade A, and why
mail 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.
How it starts
The opening of the file, as written. The whole thing — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Mail provides real-time messaging between agents. Use it alongside beads for coordinating work handoffs.
When to Use Mail vs Beads
| Use Mail | Use Beads |
|---|---|
| Real-time notifications | Persistent tasks |
| Request immediate input | Work that spans sessions |
| Announce status changes | Trackable deliverables |
| Coordinate handoffs | Dependencies between work |
Best practice: Create a bead for the work AND send mail to notify the receiving agent.
Commands
# Send a message to a context or actor
ab mail send --to AllBeadsWeb "New feature ready for review"
ab mail send --to agent@AllBeadsWeb "Task completed"
# Send different message types
ab mail send --to AllBeadsWeb --message-type notify "Build completed"
ab mail send --to AllBeadsWeb --message-type request "Please approve deployment"
ab mail send --to AllBeadsWeb --message-type broadcast "System maintenance at 5pm"
# Specify sender
ab mail send --to AllBeadsWeb --from "build-bot" "CI passed"
# Check inbox
ab mail inbox
# Check unread count
ab mail unread
# Send test messages (for verification)
ab mail test "Your message here"
# Mark messages as read
ab mail read <message-id> # Mark one as read
ab mail read --all # Mark all as read
# Archive messages
ab mail archive <message-id> # Archive one message
ab mail archive --all # Archive all read messages
# Delete messages
ab mail delete <message-id> # Permanently delete
Agent Handoff Workflow
When handing off work to another agent or repo:
1. Create the Bead (Persistent Task)
ab create --context=AllBeadsWeb --title="Implement /api/beads/import" --type=feature --priority=2
2. Send Mail Notification (Real-time Alert)
ab mail test "New task created: Implement /api/beads/import endpoint for CLI sync. See abw-079."
3. Receiving Agent Picks Up
The agent in the target repo:
ab mail inbox # Sees the notification
bd ready # Finds the task
bd update abw-079 --status=in_progress
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 · 133 lines · 8 tokens per session scan A df89426e5102
mail is a command published in the GitHub repository thrashr888/AllBeads (8 stars, last pushed 6d ago), licensed MIT. It adds 8 tokens to every session and 935 once invoked, about $0.0000 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
pm-arch
Scan project structure and generate Mermaid architecture diagrams + flowcharts under .pm/architecture/.
pm-review
Review local git diff with reasoning + snippets; cross-check; dispose findings into the rules library.
pm-charter
Create, import, discover, approve, or skip project charter. No-arg form is an interactive wizard.
pm-done
Close a todo (TODO-xxx), sync completed.md, refresh overview.
_closing
会改 .pm/ 的 /pm- 回复必须有一句中文摘要。链接只列已经存在的文件，不要指向还没生成的路径。.
star
Use the roster below to route a research-workflow request to exactly one STAR skill.