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/creategit 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/create)<a href="https://agentmods.dev/commands/thrashr888/allbeads/create"><img src="https://agentmods.dev/badge/commands/thrashr888/allbeads/create.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.00015 | $0.00627 |
| Opus 5 | $0.00008 | $0.00313 |
| Sonnet 5 | $0.00003 | $0.00125 |
| Haiku 4.5 | $0.00002 | $0.00063 |
Grade A, and why
create 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.
How it starts
The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create a new bead (issue/task) in any AllBeads context. This enables cross-repository task handoff - creating work items in other repos for other agents to pick up.
Usage
# Create in a specific context
ab create --context=<context-name> --title="<title>" --type=<type> --priority=<priority>
# Examples
ab create --context=AllBeadsWeb --title="Add new API endpoint" --type=feature --priority=2
ab create --context=AllBeadsApp --title="Fix menu bar icon" --type=bug --priority=1
ab create --context=QDOS --title="Implement parser" --type=task
Parameters
| Parameter | Required | Description |
|---|---|---|
--context |
Yes | Target context name (e.g., AllBeadsWeb, AllBeadsApp) |
--title |
Yes | Title of the bead |
--type |
No | Type: bug, feature, task, epic, chore (default: task) |
--priority |
No | Priority: P0-P4 or 0-4 (default: P2) |
Cross-Repo Task Handoff
This is the primary mechanism for distributing work across the AllBeads ecosystem:
- Identify work for another repo: While working, discover something that belongs elsewhere
- Create the bead:
ab create --context=AllBeadsWeb --title="..." --type=feature - Agent in target repo picks it up: They run
bd readyand see the task - Work flows naturally: Each repo's agent handles its own work
Common Handoff Targets
| Context | What goes there |
|---|---|
AllBeadsWeb |
Web UI features, API endpoints, dashboard work |
AllBeadsApp |
macOS app features, native UI, menu bar items |
AllBeads |
CLI features, core library, Rust code |
Workflow Example
# Working in AllBeads CLI, realize we need a web endpoint
ab create --context=AllBeadsWeb \
--title="Add /api/beads/import endpoint" \
--type=feature \
--priority=2
# The bead appears in AllBeadsWeb
ab list -C AllBeadsWeb
# Agent in AllBeadsWeb picks it up
cd ../AllBeadsWeb
bd ready
bd update abw-xxx --status=in_progress
# ... implement ...
bd close abw-xxx
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 · 70 lines · 15 tokens per session scan A 7fdff320f66c
create is a command published in the GitHub repository thrashr888/AllBeads (8 stars, last pushed 5d ago), licensed MIT. It adds 15 tokens to every session and 627 once invoked, about $0.0001 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-done
Close a todo (TODO-xxx), sync completed.md, refresh overview.
pm-charter
Create, import, discover, approve, or skip project charter. No-arg form is an interactive wizard.
pm-check
Diagnose .pm/ health (missing files, broken audit, stale map, unconfirmed PRD) and repair or increment without overwriting confirmed content.
_closing
会改 .pm/ 的 /pm- 回复必须有一句中文摘要。链接只列已经存在的文件，不要指向还没生成的路径。.
pm-checkup
On-demand five-dimension project checkup (security, function, completeness, quality, docs) with P0/P1/P2. No cron.
flow-archive
Run the canonical flow/archive Flow lifecycle.