Borrowing it
Nothing to install: this file belongs to delightful-ai/beads-rs. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/delightful-ai/beads-rs/main/.claude/skills/beads-jj-workflow/SKILL.mdgit clone --depth 1 https://github.com/delightful-ai/beads-rsWrote 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/delightful-ai/beads-rs/beads-jj-workflow)<a href="https://agentmods.dev/skills/delightful-ai/beads-rs/beads-jj-workflow"><img src="https://agentmods.dev/badge/skills/delightful-ai/beads-rs/beads-jj-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.
<a href="https://agentmods.dev/skills/delightful-ai/beads-rs/beads-jj-workflow"><img src="https://agentmods.dev/badge/skills/delightful-ai/beads-rs/beads-jj-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00029 | $0.00483 |
| Opus 5 | $0.00015 | $0.00242 |
| Sonnet 5 | $0.00006 | $0.00097 |
| Haiku 4.5 | $0.00003 | $0.00048 |
Grade A, and why
beads-jj-workflow 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 12d 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.
What it actually says
beads-rs Development Workflow
jj for version control, bd for issue tracking. Use together.
First Time This Session?
Run bd prime for a quick, dense tutorial on how beads works and how we use it.
VCS Operations
Use the /using-jj skill for all version control.
- Resolving conflicts? See the conflicts section.
- Making PRs? Read github.md first.
- Messing with the DAG? Read surgery.md.
The Loop
bd ready # see what's next
bd show bd-xyz # understand it
bd claim bd-xyz # you own it now
jj new # start first change
# --- this loop runs MANY times per bead ---
# edit: one coherent thing (add fn, fix bug, write test)
jj describe "bd-xyz: added validation for Foo"
jj new
# edit: next coherent thing
jj describe "bd-xyz: tests for Foo validation"
jj new
# ---
bd close bd-xyz # bead done, all acceptance met
JJ Rhythm
Commits are checkpoints, not milestones. The loop runs 3-20 times per bead.
- ~50 lines without
jj describe? Too much. Describe andjj new. - Touched 2+ unrelated things? Should've been 2 commits.
- About to context-switch? Describe first.
- Every commit message includes the bead ID.
Fixing mistakes:
- Batched too much?
jj split - Wrong message?
jj describeagain - Reorganize?
jj squash,jj rebase -r
Follow-up Beads
Notice out-of-scope work? File a bead immediately:
bd create "Hardcoded 30s timeout in sync.rs:234" --type=bug --priority=2
Don't just mention it in commits—make it trackable.
Verification Before Close
Before bd close:
cargo fmt --all
cargo clippy -- -D warnings
cargo test
All must pass. Then close.
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.
- 12d ago First seen · 75 lines · 29 tokens per session scan A 387ca0bda1f4
beads-jj-workflow is a skill published in the GitHub repository delightful-ai/beads-rs (24 stars, last pushed 23d ago), licensed MIT. It adds 29 tokens to every session and 483 once invoked, about $0.0001 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
gsd-quick
Execute a quick task with GSD guarantees (atomic commits, state tracking) but skip optional agents.
gsd-quick-batch
Batch several /gsd:quick-shaped tasks together — planned, dispatched, and merged as one run.
gh-issues
Fetch GitHub issues, spawn sub-agents to implement fixes and open PRs, then monitor and address PR review comments. Usage: /gh-issues [owner/repo] [--label bug] [--limit 5] [--milestone v1.0] [--assignee @me] [--fork user/repo] [--watch] [--interval 5] [--reviews-only] [--cron] [--dry-run] [--model glm-5]…
gsd-pause-work
Create context handoff when pausing work mid-phase.
gsd-ship
Create PR, run review, and prepare for merge after verification passes.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.