Commands for managing epics, which are large pieces of work divided into smaller issues. They show child-issue progress and can close an epic when all its children are complete.

Use them to check an epic’s completion, view its child issues, calculate progress, and close completed epics.

They make progress on multi-step features visible and reduce manual cleanup when the work is finished.

How NguyenSiTrung/Conductor-Beads configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to NguyenSiTrung/Conductor-Beads. 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/NguyenSiTrung/Conductor-Beads/main/.claude/skills/beads/commands/epic.md

Clone the repo

git clone --depth 1 https://github.com/NguyenSiTrung/Conductor-Beads

Made for: Claude Code.

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/commands/nguyensitrung/conductor-beads/epic/github.svg)](https://agentmods.dev/commands/nguyensitrung/conductor-beads/epic)

Your own site

<a href="https://agentmods.dev/commands/nguyensitrung/conductor-beads/epic"><img src="https://agentmods.dev/badge/commands/nguyensitrung/conductor-beads/epic/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/commands/nguyensitrung/conductor-beads/epic"><img src="https://agentmods.dev/badge/commands/nguyensitrung/conductor-beads/epic.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 3 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 216 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.

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.00003	$0.00216
Opus 5.5	$0.00001	$0.00086
Sonnet 5.5	$0.00001	$0.00043
Haiku 4.5	$0.00000	$0.00022

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

Security

Grade A, and why

epic 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 2mo 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.

.claude/skills/beads/commands/epic.md · 28 lines

What it actually says

Manage epics (large features composed of multiple issues).

Available Commands

status: Show epic completion status
- Shows progress for each epic
- Lists child issues and their states
- Calculates completion percentage
close-eligible: Close epics where all children are complete
- Automatically closes epics when all child issues are done
- Useful for bulk epic cleanup

Epic Workflow

Create epic: bd create "Large Feature" -t epic -p 1
Link subtasks: bd dep add bd-20 bd-10 --type parent-child (task bd-20 is child of epic bd-10)
- Or at creation: bd create "Subtask title" -t task --parent bd-10
Track progress: bd epic status
Auto-close when done: bd epic close-eligible

Epics use parent-child dependencies to track subtasks.

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.

2mo ago First seen · 28 lines · 3 tokens per session scan A b31ffcfc2a42

Subscribe to this mod's changes

epic is a command published in the GitHub repository NguyenSiTrung/Conductor-Beads (23 stars, last pushed 8mo ago), licensed Apache-2.0. It adds 3 tokens to every session and 216 once invoked, about $0.0000 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.

Project management

epic next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
epicNguyenSiTrung/Conductor-Beads	Command	23	8mo ago	Apache-2.0	A	3	Claude Code
checklistgithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	yesterday	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	yesterday	MIT	A	26	Claude Code
convergegithub/spec-kit	Command	148k	yesterday	MIT	A	35	Claude Code
implementgithub/spec-kit	Command	148k	yesterday	MIT	A	14	Claude Code

Conductor-Beads: Command for Claude Code