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/syncgit 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/sync)<a href="https://agentmods.dev/commands/thrashr888/allbeads/sync"><img src="https://agentmods.dev/badge/commands/thrashr888/allbeads/sync.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.00139 |
| Opus 5 | $0.00003 | $0.00069 |
| Sonnet 5 | $0.00001 | $0.00028 |
| Haiku 4.5 | $0.00001 | $0.00014 |
Grade A, and why
sync 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 3d 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
Synchronize AllBeads contexts with their git remotes.
Commands:
allbeads sync- Sync the AllBeads config (if in git)allbeads sync --all- Sync all context beadsallbeads sync <context>- Sync a specific contextallbeads sync --status- Check sync status without syncing
This fetches the latest beads from each repository's remote and updates the local cache.
Run this:
- At the start of a session to get latest state
- After making changes in multiple repos
- Before generating cross-repo reports
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.
- 3d ago First seen · 19 lines · 7 tokens per session scan A 983efc92f829
sync is a command published in the GitHub repository thrashr888/AllBeads (8 stars, last pushed 4d ago), licensed MIT. It adds 7 tokens to every session and 139 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.
_closing
会改 .pm/ 的 /pm- 回复必须有一句中文摘要。链接只列已经存在的文件，不要指向还没生成的路径。.
new
Creates a new item in a module that supports the new capability.
flow-archive
Run the canonical flow/archive Flow lifecycle.