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 skills/mburdo/knowledge_and_vibes/beads-clinpx skills add Mburdo/knowledge_and_vibes --skill beads-cligit 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/skills/mburdo/knowledge_and_vibes/beads-cli)<a href="https://agentmods.dev/skills/mburdo/knowledge_and_vibes/beads-cli"><img src="https://agentmods.dev/badge/skills/mburdo/knowledge_and_vibes/beads-cli.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.00045 | $0.00949 |
| Opus 5 | $0.00023 | $0.00475 |
| Sonnet 5 | $0.00009 | $0.00190 |
| Haiku 4.5 | $0.00005 | $0.00095 |
Grade A, and why
beads-cli 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Beads CLI (bd)
Task tracking across sessions. All issue tracking goes through bd.
When This Applies
| Signal | Action |
|---|---|
| Need to create a task | bd create |
| Looking for work | bd ready --json |
| Claiming a task | bd update --status in_progress |
| Finishing a task | bd close |
| Managing dependencies | bd dep add/tree |
Core Workflow
# Finding work
bd ready --json # Unblocked tasks ready for work
bd blocked # Tasks waiting on dependencies
bd list # All tasks
# Task lifecycle
bd create "Title" -t bug -p 1 # Create with type, priority
bd update bd-42 --status in_progress --assignee YOUR_NAME # Claim
bd close bd-42 --reason "Completed: summary" # Complete
# Viewing
bd show bd-42 # Full task details
bd info # Project summary
Dependencies
bd dep add bd-child bd-blocker --type blocks # Child blocked by blocker
bd dep add bd-a bd-b --type related # Related tasks
bd dep add bd-child bd-parent --type parent-child # Hierarchy
bd dep add bd-new bd-old --type discovered-from # Found during work
bd dep tree bd-42 # Visualize dependencies
bd dep cycles # Find circular deps
Task Types and Priority
| Type | Use For |
|---|---|
bug |
Defects, errors |
feature |
New functionality |
task |
General work items |
epic |
Parent/container beads |
chore |
Maintenance, cleanup |
| Priority | Meaning |
|---|---|
0 |
Critical (do first) |
1 |
High |
2 |
Normal |
3 |
Low |
4 |
Backlog |
Child Beads
Hierarchical IDs: bd-a1b2.1, bd-a1b2.3.1
bd create "Sub-task" --parent bd-123 -p 1
Claiming Protocol (Multi-Agent)
CRITICAL: Always claim parent AND all sub-beads together.
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 · 150 lines · 45 tokens per session scan A 9a028f2ef78f
beads-cli is a skill published in the GitHub repository Mburdo/knowledge_and_vibes (44 stars, last pushed 8mo ago), licensed MIT. It adds 45 tokens to every session and 949 once invoked, about $0.0002 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-30.
Other skills, from other repositories
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
timeline-creator
Create HTML timelines and project roadmaps with Gantt charts, milestones, phase groupings, and progress indicators. Use when users request timelines, roadmaps, Gantt charts, project schedules, or milestone visualizations.
pm-all
Skill "pm-all" from wei63w/pm-manager, covering user input, outline and shared workflow (all /pm- commands).
bootstrap-prd
Set up PRD-driven development infrastructure for a new project, including directory structure, templates, and roadmap.
simulator-reactions
Simulator.Company reactions specialist — comments, events, approvals, ratings and other feedback attached under an actor. Use when the user wants to comment on an actor, reply in a thread, read/like/pin the discussion, mark comments read, or get reaction stats. Activate when the user says "comment on this actor"…
glab-issue
Create, view, update, and manage GitLab issues. Use when working with issue tracking, bug reports, feature requests, or task management. Operations include creating issues, listing with filters, viewing details, adding comments/notes, updating labels/assignees/milestones, closing/reopening, and board management.…