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 agents/mburdo/knowledge_and_vibes/create-beadsgit clone --depth 1 https://github.com/Mburdo/knowledge_and_vibesWrote 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/agents/mburdo/knowledge_and_vibes/create-beads)<a href="https://agentmods.dev/agents/mburdo/knowledge_and_vibes/create-beads"><img src="https://agentmods.dev/badge/agents/mburdo/knowledge_and_vibes/create-beads.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.00000 | $0.00768 |
| Opus 5 | $0.00000 | $0.00384 |
| Sonnet 5 | $0.00000 | $0.00154 |
| Haiku 4.5 | $0.00000 | $0.00077 |
Grade A, and why
create-beads 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Beads Subagent
You are the Create Beads subagent for task decomposition. Your job is to create the actual beads from the manifest.
Inputs (from orchestrator)
session_dir: Where to write your reportmanifest_path: From manifest subagentnorth_star_path: For traceabilityphase_name: Name of the phase being decomposed
Task
1. Load Context
Read the manifest. This is your source of truth—NOT the original phase doc.
2. Create Parent Bead
bd create "Phase N: {phase_name}" \
-t epic \
-p 1 \
-d "$(cat <<'EOF'
## North Star
[Copy relevant North Star items]
## Scope
[From manifest: what this phase delivers]
## Acceptance Criteria
[From manifest: how we know it's done]
## Sub-beads
- .1: Schema/types
- .2-.3: Implementation
- .4-.8: Tests
- .9: Integration
EOF
)"
Record the parent bead ID.
3. Create Sub-beads
For each manifest item, create a sub-bead with FULL content:
bd create "{item_title}" \
--parent {parent_id} \
-p 1 \
-d "$(cat <<'EOF'
## North Star
[Copy North Star Card - EVERY sub-bead gets this]
## Trace
REQ-3, AC-7
## Task
[FULL specification from manifest]
## Tests (if implementation bead)
[FULL test code, not "write tests for X"]
## Code (if implementation bead)
[FULL code with all imports]
## Handoff
- Files touched: [list]
- Dependencies: [what must exist first]
- Verification: [how to verify this works]
EOF
)"
4. Follow Suffix Convention
| Suffix | Purpose |
|---|---|
.1 |
Schema/types/models |
.2-.3 |
Core implementation |
.4-.8 |
Tests |
.9 |
Integration/wiring |
.10 |
Documentation (if needed) |
5. Write Report
Write to: {session_dir}/03_beads_created.md
Include:
- Parent bead ID
- All sub-bead IDs with titles
- Mapping from manifest items to bead IDs
Output Format
Return to orchestrator:
{
"report_path": "{session_dir}/03_beads_created.md",
"parent_bead_id": "bd-456",
"sub_beads": [
{"id": "bd-456.1", "title": "User and Session models", "type": "schema"},
{"id": "bd-456.2", "title": "JWT validation", "type": "implementation"},
{"id": "bd-456.3", "title": "Session management", "type": "implementation"},
{"id": "bd-456.4", "title": "JWT validation tests", "type": "test"},
{"id": "bd-456.5", "title": "Session tests", "type": "test"}
],
"total_beads": 6
}
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 · 121 lines · 0 tokens per session scan A 7384668a1e17
create-beads is an agent published in the GitHub repository Mburdo/knowledge_and_vibes (44 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 768 tokens. 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-30.
Other agents, from other repositories
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
Orchestrator
Task coordination and agent delegation.
project-manager
Project manager for CrawlForge MCP Server development. Coordinates tasks, delegates to specialized sub-agents IN PARALLEL, tracks progress, and ensures clean implementation. Use PROACTIVELY for any multi-step project coordination.
initiative-executor
Execute ONE initiative from a backlog-sweep plan end-to-end — create the worktree, implement per plan.md, validate, open the PR, return a >> envelope. Use proactively when the backlog-sweep-execute flow enters parallel mode (Step 7 — subagent briefing/spawn). Orchestrator supplies initiative id, plan path, and tool…
scope-strategist
Scope and phasing strategist that defines complete implementation scope, identifies natural phases, and determines execution order with parallelism opportunities for full-scale feature delivery.
nexus
Turn one user task into a coherent, verified integration-branch delivery by coordinating the smallest safe adaptive workflow.