work-beads

work-beads is a skill for Claude Code from zigrivers/scaffold. It costs 25 tokens per session (881 once invoked), scanned A, original, MIT.

A workflow for completing tasks from a project’s Beads queue, an issue list where work items can be claimed and tracked through completion.

In plain words
What is it for?
Use it to pick up one or more backlog tasks, build them in separate worktrees, verify the changes, send them through review, and enqueue them for merging.
Why use it?
It coordinates claiming, isolated development, checking, review, merging, and closing tasks so work does not overlap or get left unfinished.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions AGENTS.md; mentions Cursor.

Part of the scaffold plugin — 5 skills, 1 hook shipped together

Good fit Use it to pick up one or more backlog tasks, build them in separate worktrees, verify the changes, send them through review, and enqueue them for merging.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/zigrivers/scaffold/work-beads
Install

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.

Any agent
npx skills add zigrivers/scaffold --skill work-beads
Clone the repo
git clone --depth 1 https://github.com/zigrivers/scaffold

Made for: Claude Code.

Or install scaffold, the plugin that ships this one along with the rest of its 5 skills, 1 hook.

Wrote 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.

agentmods badge for work-beads

README.md
[![agentmods](https://agentmods.dev/badge/skills/zigrivers/scaffold/work-beads/github.svg)](https://agentmods.dev/skills/zigrivers/scaffold/work-beads)
Your own site
<a href="https://agentmods.dev/skills/zigrivers/scaffold/work-beads"><img src="https://agentmods.dev/badge/skills/zigrivers/scaffold/work-beads/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.

agentmods 80×15 button for work-beads

Your own site · 80×15
<a href="https://agentmods.dev/skills/zigrivers/scaffold/work-beads"><img src="https://agentmods.dev/badge/skills/zigrivers/scaffold/work-beads.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 25 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 881 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 2 findings, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • high Prompt Injection · line 6
    Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
    Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
  • medium Excessive Agency · line 29
    Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
    Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00025 $0.00881
Opus 5.5 $0.00010 $0.00352
Sonnet 5.5 $0.00005 $0.00176
Haiku 4.5 $0.00003 $0.00088

Measured 1mo ago against content hash a673a380231a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

work-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 1mo 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.

content/agent-skills/work-beads/SKILL.md · 69 lines

How it starts

The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Work Beads

Work the requested Beads queue with the ship loop. Preserve the atomic claim, lease, verification, review, and queue contracts across agents.

The loop contract:

set identity once, then repeat up to N times (one bead in flight per agent):
  refresh view -> select ONE bead -> claim atomically, then validate (lost the
  claim? next candidate; dup/conflict? cooldown-release + next) -> worktree
  -> build (draft PR on first push; renew lease on each push)
  -> verify (make check-affected) -> review (mmr, max 3 rounds per cycle)
  -> enqueue (make mq-enqueue) and move on -> daemon lands + closes the bead
batch end (budget spent, queue drained, or an external stop): report in the slots

The agent's finish line is a green gate + passing review + the PR ENQUEUED — the merge-queue daemon batches, lands, and closes the bead; do not wait for the merge or bd close an enqueued bead yourself. (No merge queue installed? Land via the serialized merge slot instead — same finish line, you just do the merge.) Standing authorization: run the whole loop without asking permission. Do not end your turn after opening a draft PR with a list of "next steps" — that is the #1 observed agent failure. Stop when the user asks to stop. Otherwise, the only mid-loop stops are a true external dependency, missing credentials or authority, a destructive action, a material product decision outside the acceptance criteria, or a demonstrated technical plateau after safe approaches are exhausted. An unresolved required-safeguard defect is not a plateau; an in-scope blocker starts or continues remediation.

Each review cycle has at most three rounds. A genuine round-three in-scope or required-safeguard blocker starts a new cycle only after a concrete repair, focused regression proof, and the required gate; review the new exact head from round one. Duplicate, stale, hypothetical, speculative, cosmetic, and already- dispositioned findings cannot restart review. No owner approval is required for in-scope remediation. Merge only when the final exact head meets the channel floor, all required gates pass, every finding is dispositioned, and no verified blocker remains.

Invocation: /work-beads (1 bead) · /work-beads N (up to N beads, selected one at a time at claim time — N is a budget, not a reservation; never pre-pick a list) · /work-beads N <label> (same, scoped to a label) · /work-beads <id> [<id>...] (explicit IDs, worked in dependency order). For the detailed phase procedures, load the router in .agents/skills/work-beads/SKILL.md when reading this as an AGENTS.md or Cursor rule.

Read the full file on GitHub · 69 lines

Files

What ships with it

4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

  1. 1mo ago Changed · -463 lines · -81 tokens per session a673a380231a
  2. 1mo ago Changed · +27 lines e8c9e0e549fa
  3. 1mo ago First seen · 505 lines · 106 tokens per session scan A d0a81b05f94b

Subscribe to this mod's changes

work-beads is a skill published in the GitHub repository zigrivers/scaffold (6 stars, last pushed 1mo ago), licensed MIT. It adds 25 tokens to every session and 881 once invoked, about $0.0001 per session on Opus 5.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.