What is managing-beads?

A workflow for managing project issues with Beads, a tracker whose issues are stored in a file and moved through Git. It covers finding available work, claiming issues, updating their status, creating follow-up work, and closing completed issues.

Use it to inspect available issues, claim tasks, create new issues, update progress, close finished work, and synchronize issue data before context compaction.

It gives the team a consistent way to record, assign, synchronize, and finish development work.

How andrzejchm/fdb configures OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to andrzejchm/fdb. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/andrzejchm/fdb/main/.opencode/skills/managing-beads/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/andrzejchm/fdb

Made for: OpenCode.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/andrzejchm/fdb/managing-beads/github.svg)](https://agentmods.dev/skills/andrzejchm/fdb/managing-beads)

Your own site

<a href="https://agentmods.dev/skills/andrzejchm/fdb/managing-beads"><img src="https://agentmods.dev/badge/skills/andrzejchm/fdb/managing-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/andrzejchm/fdb/managing-beads"><img src="https://agentmods.dev/badge/skills/andrzejchm/fdb/managing-beads.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 53 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 715 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 pass 7 Sept 2026

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.

Model	Per session	Once invoked
Fable 5.1	$0.00053	$0.00715
Opus 5.5	$0.00021	$0.00286
Sonnet 5.5	$0.00011	$0.00143
Haiku 4.5	$0.00005	$0.00072

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

Security

Grade A, and why

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

.opencode/skills/managing-beads/SKILL.md · 73 lines

How it starts

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

Managing Beads Issues

Session workflow

Run bd prime — loads context and shows open/claimed issues.
Pick work with bd ready, claim with bd update <id> --claim.
Work on code. Create follow-up issues as you discover them.
Commit issues.jsonl together with the code it tracks (the pre-commit hook exports it automatically).
Before context compaction: run bd sync to flush any pending writes.
Close finished issues with bd close <id>.

Core commands

bd prime                                                          # Session start: load context
bd ready                                                          # List unclaimed available issues
bd show <id>                                                      # View issue details
bd update <id> --claim                                            # Claim an issue
bd update <id> --status=in-progress                               # Update status
bd create --title="..." --description="..." --type=task --priority=2  # Create an issue
bd close <id>                                                     # Mark issue done
bd sync                                                           # Flush pending writes (before compaction)
bd bootstrap                                                      # Rebuild local DB after git pull
bd github sync                                                    # Bidirectional sync with GitHub Issues
bd github sync --pull-only                                        # Pull from GitHub only
bd github sync --push-only                                        # Push to GitHub only

Creating issues

bd create \
  --title="Add scroll support for web" \
  --description="CDP-based scroll not yet implemented; fdb scroll fails on web targets." \
  --type=task \
  --priority=2

Types: task, bug, feature, chore
Priorities: 1 (critical) → 4 (low)

Rules

On main: git add .beads/issues.jsonl && git commit directly — the pre-commit hook exports to the right place.
Always commit issues.jsonl together with the code changes it tracks — never in isolation.
Run bd bootstrap after git pull on any machine that already has a local DB.
Run bd prime at session start only — not during compaction (bd sync handles compaction).
Never run bd doctor --fix — it can corrupt the local DB.
bd is the source of truth; GitHub Issues are a mirror — sync with bd github sync.
Capture any work discovered during implementation as new issues immediately.

Read the full file on GitHub · 73 lines

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.

1mo ago First seen · 73 lines · 53 tokens per session scan A 5e1f949808a7

Subscribe to this mod's changes

managing-beads is a skill published in the GitHub repository andrzejchm/fdb (46 stars, last pushed 12d ago), licensed MIT. It adds 53 tokens to every session and 715 once invoked, about $0.0002 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-30.

Git and workflow Project management

antfu-issue-triage

Triage open issues and PRs of the current GitHub repo - find already-fixed, duplicate, and spam items, suggest labels, gauge demand from reactions and comments, then present a table of proposed actions and comments for confirmation before touching anything. Use when asked to triage, organize, clean up, or groom issues…

antfu/skills · 76 tokens

mcore-split-pr

Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.

NVIDIA/skills · 25 tokens

engineer-bot-ops

A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.

makecindy/cindy · 57 tokens

shiplog

Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.

aeonfun/aeon · 46 tokens

connect

Choose which wiki this session uses, the team project's pages on the Nimbalyst server or the project's local wiki of files, and connect a repository to its team project. Use at the start of a task before any wiki tool, when a wiki tool returns reponotbound, ambiguousproject, pinmismatch, projectnotaccessible…

nimbalyst/nimbalyst · 101 tokens

llxprt-issue-workflow

Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the zai-glm-flash smoke test), open code review (ocr)…

vybestack/llxprt-code · 88 tokens

fdb: Skill for OpenCode