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 skills add Mburdo/knowledge_and_vibes --skill beads-viewergit 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-viewer)<a href="https://agentmods.dev/skills/mburdo/knowledge_and_vibes/beads-viewer"><img src="https://agentmods.dev/badge/skills/mburdo/knowledge_and_vibes/beads-viewer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/mburdo/knowledge_and_vibes/beads-viewer"><img src="https://agentmods.dev/badge/skills/mburdo/knowledge_and_vibes/beads-viewer.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00053 | $0.00784 |
| Opus 5 | $0.00026 | $0.00392 |
| Sonnet 5 | $0.00011 | $0.00157 |
| Haiku 4.5 | $0.00005 | $0.00078 |
Grade A, and why
beads-viewer 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 9d 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Beads Viewer (bv)
Graph analysis layer for the Beads task graph. Precomputes metrics like PageRank and critical path.
When This Applies
| Signal | Action |
|---|---|
| "What should I work on?" | bv --robot-triage |
| Need single best task | bv --robot-next |
| Multi-agent partitioning | bv --robot-triage --robot-triage-by-track |
| Risk/hygiene check | bv --robot-alerts |
| Finding blockers | bv --robot-blocker-chain |
CRITICAL RULE
Always use --robot-* flags. Never run bare bv.
Bare bv launches a TUI that will hang AI agents.
Session Kickoff
# Default (fast)
bv --robot-next # Single best next task
# Full triage bundle
bv --robot-triage # Blockers, quick wins, commands
Multi-Agent Partitioning
# Split work by parallel tracks
bv --robot-triage --robot-triage-by-track
# Track details + what each task unblocks
bv --robot-plan
Risk & Hygiene
Use before starting "big" work:
bv --robot-alerts # Stale issues, blocking cascades, drift
bv --robot-suggest # Duplicates, missing deps, cycle breaks
Debugging & Analysis
# What changed recently?
bv --robot-diff --diff-since HEAD~5
# Historical state
bv --as-of HEAD~10 --robot-triage
# Blocker analysis
bv --robot-blocker-chain bd-123
# Impact analysis before refactor
bv --robot-impact path/to/file1,path/to/file2
bv --robot-file-relations path/to/core_file
Handoff / Audit Trail
bv --robot-history --bead-history bd-123
Semantic Search
bv --search "your query" --robot-search
Graph Metrics Explained
| Metric | Meaning | Use For |
|---|---|---|
| PageRank | Foundational blockers | Tasks that enable many others |
| Betweenness | Bottlenecks | Must pass through these |
| Critical Path | Longest dependency chain | Overall timeline |
Keeping bv Current
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.
- 9d ago First seen · 146 lines · 53 tokens per session scan A e3eaea593c61
beads-viewer is a skill published in the GitHub repository Mburdo/knowledge_and_vibes (44 stars, last pushed 8mo ago), licensed MIT. It adds 53 tokens to every session and 784 once invoked, about $0.0003 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.