A project rule that uses Beads, a command-line issue tracker, to record tasks, bugs, dependencies, and their status.

Use it to create and claim tasks, link dependencies, close completed work, list open issues, and sync issue data with the Git remote.

It keeps work items in one trackable system instead of scattered TODO notes, and helps show which tasks are ready or blocked.

beads — Cursor rule for Cursor by jordanhubbard: A project rule that uses Beads, a command-line issue…

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.

agentmods

npx agentmods add rules/jordanhubbard/ai-code-reviewer/beads

Clone the repo

git clone --depth 1 https://github.com/jordanhubbard/ai-code-reviewer

Made for: Cursor.

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/rules/jordanhubbard/ai-code-reviewer/beads.svg)](https://agentmods.dev/rules/jordanhubbard/ai-code-reviewer/beads)

Your own site

<a href="https://agentmods.dev/rules/jordanhubbard/ai-code-reviewer/beads"><img src="https://agentmods.dev/badge/rules/jordanhubbard/ai-code-reviewer/beads.svg" alt="Measured on agentmods" height="20"></a>

Per session 360 This file is loaded in full into every session.

When invoked 360 The same file — it is already loaded in full.

Security scan A 0 findings. Scan, not verified.

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	$0.00360	$0.00360
Opus 5	$0.00180	$0.00180
Sonnet 5	$0.00072	$0.00072
Haiku 4.5	$0.00036	$0.00036

Measured 4d ago against content hash 1c829a26dd4e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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 4d 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.

.cursor/rules/beads.mdc · 39 lines

What it actually says

Beads Issue Tracking

Auto-generated by 'bd setup cursor' - do not remove these markers

BEGIN BEADS INTEGRATION

This project uses Beads (bd) for issue tracking.

Core Rules

Track ALL work in bd (never use markdown TODOs or comment-based task lists)
Use bd ready to find available work
Use bd create to track new issues/tasks/bugs
Use bd sync at end of session to sync with git remote
Git hooks auto-sync on commit/merge

Quick Reference

bd prime                              # Load complete workflow context
bd ready                              # Show issues ready to work (no blockers)
bd list --status=open                 # List all open issues
bd create --title="..." --type=task  # Create new issue
bd update <id> --status=in_progress  # Claim work
bd close <id>                         # Mark complete
bd dep add <issue> <depends-on>       # Add dependency (issue depends on depends-on)
bd sync                               # Sync with git remote

Workflow

Check for ready work: bd ready
Claim an issue: bd update <id> --status=in_progress
Do the work
Mark complete: bd close <id>
Sync: bd sync (or let git hooks handle it)

Context Loading

Run bd prime to get complete workflow documentation in AI-optimized format (~1-2k tokens).

For detailed docs: see AGENTS.md, QUICKSTART.md, or run bd --help

END BEADS INTEGRATION

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.

4d ago First seen · 39 lines · 360 tokens per session scan A 1c829a26dd4e

Subscribe to this mod's changes

beads is a cursor rule published in the GitHub repository jordanhubbard/ai-code-reviewer (44 stars, last pushed 3mo ago), licensed BSD-2-Clause. It adds 360 tokens to every session, about $0.0018 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.

Project management

beads

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

Beads Issue Tracking

Auto-generated by 'bd setup cursor' - do not remove these markers

BEGIN BEADS INTEGRATION

Core Rules

Quick Reference

Workflow

Context Loading

END BEADS INTEGRATION

What this file has done since we first saw it

Other cursor rules, from other repositories

development-workflow

feedback-enhanced

project-onboarding-rule

linear-in-review

sprint-planning

generate-tasks