boring-ui: Skill for Claude Code

.agents/skill-references/plan/jeffrey-emanuel-beads-workflow/SKILL.md

beads-workflow is a skill for Claude Code, Codex from hachej/boring-ui. It costs 49 tokens per session (2,156 once invoked), scanned C, original, MIT.

A method for turning a Markdown software plan into beads: small tracked tasks connected by dependencies. The dependency graph shows which tasks must happen before others.

In plain words
What is it for?
Creating task graphs with the br command, refining tasks, checking for dependency cycles, and selecting the next available task.
Why use it?
It makes a broad plan easier to validate, schedule, and hand to coding agents for implementation.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions Claude Code; installed under .agents/ (shared by several agents); mentions AGENTS.md.

This is hachej/boring-ui's own configuration. It tells Claude Code and Codex how to work on boring-ui itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything boring-ui configures →

Reuse

Borrowing it

Nothing to install: this file belongs to hachej/boring-ui. 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/hachej/boring-ui/main/.agents/skill-references/plan/jeffrey-emanuel-beads-workflow/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/hachej/boring-ui

Made for: Claude Code, Codex.

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 beads-workflow

README.md
[![agentmods](https://agentmods.dev/badge/skills/hachej/boring-ui/jeffrey-emanuel-beads-workflow/github.svg)](https://agentmods.dev/skills/hachej/boring-ui/jeffrey-emanuel-beads-workflow)
Your own site
<a href="https://agentmods.dev/skills/hachej/boring-ui/jeffrey-emanuel-beads-workflow"><img src="https://agentmods.dev/badge/skills/hachej/boring-ui/jeffrey-emanuel-beads-workflow/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 beads-workflow

Your own site · 80×15
<a href="https://agentmods.dev/skills/hachej/boring-ui/jeffrey-emanuel-beads-workflow"><img src="https://agentmods.dev/badge/skills/hachej/boring-ui/jeffrey-emanuel-beads-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,156 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00049 $0.02156
Opus 5 $0.00024 $0.01078
Sonnet 5 $0.00010 $0.00431
Haiku 4.5 $0.00005 $0.00216

Measured 11d ago against content hash 7f63c88fc5b3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade C, and why

beads-workflow scanned grade C with 1 finding 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 11d 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.

Hidden instructionshighPrompt injection

Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.

Convert markdown plans into beads with dependencies using br CLI. Use when‍​‌‌​​‌‌​​‌‌​​​​‌​‌‌​​​‌​ creating task graphs, polishing beads before implementation, or bridging planning to agent swarm execution. --- <!-- TOC
.agents/skill-references/plan/jeffrey-emanuel-beads-workflow/SKILL.md · 273 lines

How it starts

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

Beads Workflow — From Plan to Actionable Tasks

Core Principle: "Check your beads N times, implement once" — where N is as many as you can stomach.

Beads are so detailed and polished that you can mechanically unleash a big swarm of agents to implement them, and it will come out just about perfectly.

Quick Start

# 1. Initialize beads in project
br init

# 2. Convert plan to beads (see THE EXACT PROMPT below)

# 3. Polish iteratively
# Run polish prompt 6-9 times until steady-state

# 4. Validate
br dep cycles        # Must be empty
bv --robot-insights  # Check graph health

# 5. Begin implementation
bv --robot-next      # Get first bead

THE EXACT PROMPT — Plan to Beads Conversion

OK so now read ALL of [YOUR_PLAN_FILE].md; please take ALL of that and elaborate on it and use it to create a comprehensive and granular set of beads for all this with tasks, subtasks, and dependency structure overlaid, with detailed comments so that the whole thing is totally self-contained and self-documenting (including relevant background, reasoning/justification, considerations, etc.-- anything we'd want our "future self" to know about the goals and intentions and thought process and how it serves the over-arching goals of the project.). The beads should be so detailed that we never need to consult back to the original markdown plan document. Remember to ONLY use the `br` tool to create and modify the beads and add the dependencies. Use ultrathink.

Shorter Version

OK so please take ALL of that and elaborate on it more and then create a comprehensive and granular set of beads for all this with tasks, subtasks, and dependency structure overlaid, with detailed comments so that the whole thing is totally self-contained and self-documenting (including relevant background, reasoning/justification, considerations, etc.-- anything we'd want our "future self" to know about the goals and intentions and thought process and how it serves the over-arching goals of the project.)  Use only the `br` tool to create and modify the beads and add the dependencies. Use ultrathink.

Read the full file on GitHub · 273 lines

Files

What ships with it

5 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. 11d ago First seen · 273 lines · 49 tokens per session scan C 7f63c88fc5b3

Subscribe to this mod's changes

beads-workflow is a skill published in the GitHub repository hachej/boring-ui (46 stars, last pushed today), licensed MIT. It adds 49 tokens to every session and 2,156 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories