A set of project rules for using Beads, a command-line issue tracker, to record work. It defines commands for finding, creating, claiming, updating, closing, and synchronising issues.

Use it to manage tasks, bugs, dependencies, and handoffs in a repository that uses Beads. Use its commands to see available work and update issue status.

It prevents work from being hidden in markdown TODO lists or comments. It also sets rules for dependencies and for requiring permission before commits, pushes, or remote synchronisation.

beads — Cursor rule for Cursor by kunwarVivek

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.

Clone the repo

git clone --depth 1 https://github.com/kunwarVivek/mcp-github-project-manager

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/kunwarvivek/mcp-github-project-manager/beads/github.svg)](https://agentmods.dev/rules/kunwarvivek/mcp-github-project-manager/beads)

Your own site

<a href="https://agentmods.dev/rules/kunwarvivek/mcp-github-project-manager/beads"><img src="https://agentmods.dev/badge/rules/kunwarvivek/mcp-github-project-manager/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/rules/kunwarvivek/mcp-github-project-manager/beads"><img src="https://agentmods.dev/badge/rules/kunwarvivek/mcp-github-project-manager/beads.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

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

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.00596	$0.00596
Opus 5.5	$0.00238	$0.00238
Sonnet 5.5	$0.00119	$0.00119
Haiku 4.5	$0.00060	$0.00060

Measured 3d ago against content hash 6b6ad52e515d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 3d 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.

Origin

Copies of this mod

3 near-identical copies found in the catalogue:

beads — 100% identical, 0 lines differ
beads — 100% identical, 0 lines differ
beads — 100% identical, 0 lines differ

.cursor/rules/beads.mdc · 68 lines

How it starts

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

Beads Issue Tracking

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
Treat commit, push, and Dolt remote sync as policy-controlled handoff actions
Run bd prime for complete workflow context (SSOT for operational commands)
Default to conservative git authority: report status and proposed commands unless the user, orchestrator, or repository profile explicitly authorizes commit/sync/push

Quick Reference

bd prime                              # Load complete workflow context (SSOT)
bd ready                              # Show issues ready to work (no blockers)
bd list --status=open                 # List all open issues
bd create "title" -t task -p 2        # Create new issue
bd update <id> --claim                # Claim work atomically
bd unclaim <id>                       # Release stuck issue (agent crashed)
bd close <id>                         # Mark complete
bd dep add <issue> <depends-on>       # Add dependency
bd dolt push                          # Sync with remote when authorized

Workflow

Check for ready work: bd ready
Claim an issue atomically: bd update <id> --claim
Do the work
Mark complete: bd close <id>
Handoff: report changed files, validation, issue status, and any proposed commit/sync/push commands

Issue Types

bug - Something broken
feature - New functionality
task - Work item (tests, docs, refactoring)
epic - Large feature with subtasks
chore - Maintenance (dependencies, tooling)

Priorities

0 - Critical (security, data loss, broken builds)
1 - High (major features, important bugs)
2 - Medium (default, nice-to-have)
3 - Low (polish, optimization)
4 - Backlog (future ideas)

Read the full file on GitHub · 68 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.

3d ago First seen · 68 lines · 596 tokens per session scan A 6b6ad52e515d

Subscribe to this mod's changes

beads is a cursor rule published in the GitHub repository kunwarVivek/mcp-github-project-manager (104 stars, last pushed yesterday), licensed MIT. It adds 596 tokens to every session, about $0.0024 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-11-03.

Project Management Project management agent-orchestration ai github-projects mcp mcp-server

beads next to 6 cursor rules from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
beadskunwarVivek/mcp-github-project-manager	Cursor rule	104	yesterday	MIT	A	596	Cursor
github-climetagit-ai/metagit-cli	Cursor rule	4	3d ago	MIT	A	240	Cursor
project-levelmetagit-ai/metagit-cli	Cursor rule	4	3d ago	MIT	A	1,340	Cursor
cursorRuleAgileLuminary/mcp-agile-luminary	Cursor rule	3	1y ago	MIT	A	402	Cursor
dev_workflowasachs01/float-mcp	Cursor rule	2	8mo ago	MIT	A	6,887	Cursor
self_improveasachs01/float-mcp	Cursor rule	2	8mo ago	MIT	A	530	Cursor
cursor_rulesasachs01/float-mcp	Cursor rule	2	8mo ago	MIT	A	375	Cursor