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/workflowgit 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/workflow)<a href="https://agentmods.dev/commands/thrashr888/allbeads/workflow"><img src="https://agentmods.dev/badge/commands/thrashr888/allbeads/workflow.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.00007 | $0.00540 |
| Opus 5 | $0.00003 | $0.00270 |
| Sonnet 5 | $0.00001 | $0.00108 |
| Haiku 4.5 | $0.00001 | $0.00054 |
Grade A, and why
workflow 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AllBeads Workflow Guide
The Big Picture
[GitHub Repos] → [ab scan] → [ab onboard] → [AllBeads Contexts]
↓
[ab context new] → [New Repo] → [bd init] → [Managed Context]
↓
[Planning] → [bd create epics] → [Add specs] → [Ready for work]
↓
[ab ready] → [Claim task] → [Implement] → [ab close] → [Push]
Workflow Phases
1. Discovery
Find repos to manage:
ab scan github <username> # Your repos
ab scan github <org> # Org repos
ab context list # Already managed
2. Onboarding
Bring repos into AllBeads:
# Existing repo
ab onboard <repo-url>
# New repo
ab context new <name> --private
3. Planning
Create work items with specs:
bd create --title="..." --type=epic
bd comments add <id> "<spec>"
4. Execution
Complete the work:
ab ready # Find work
ab update <id> --status=in_progress
# ... implement ...
ab close <id>
git push
5. Governance
Maintain quality:
ab governance check # Policy compliance
ab agents list # Agent coverage
ab stats # Health metrics
Key Commands by Phase
| Phase | Command | Purpose |
|---|---|---|
| Discovery | ab scan github |
Find repos |
| Onboarding | ab onboard |
Add to AllBeads |
| Planning | ab context new |
Create new repo |
| Planning | bd create |
Create work items |
| Execution | ab ready |
Find work |
| Execution | ab close |
Complete work |
| Governance | ab governance check |
Verify policies |
Session Protocol
Every session should:
ab prime- Load contextab ready- Find work- Work on tasks
bd sync- Save beadsgit push- Push changes
See Also
AGENTS.md- Quick agent referenceCLAUDE.md- Full project guide/prime- Context priming/ready- Ready work
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 · 91 lines · 7 tokens per session scan A 1b07abafff13
workflow is a command published in the GitHub repository thrashr888/AllBeads (8 stars, last pushed 5d ago), licensed MIT. It adds 7 tokens to every session and 540 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-done
Close a todo (TODO-xxx), sync completed.md, refresh overview.
pm-status
Show governance health, wizard next step, all open blocking/high todos, and pending review count. Primary daily entry.
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.