Borrowing it
Nothing to install: this file belongs to jmanhype/speckit. 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/jmanhype/speckit/main/.claude/agents/beads-sync.mdgit clone --depth 1 https://github.com/jmanhype/speckitWrote 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/agents/jmanhype/speckit/beads-sync)<a href="https://agentmods.dev/agents/jmanhype/speckit/beads-sync"><img src="https://agentmods.dev/badge/agents/jmanhype/speckit/beads-sync/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/agents/jmanhype/speckit/beads-sync"><img src="https://agentmods.dev/badge/agents/jmanhype/speckit/beads-sync.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00015 | $0.00789 |
| Opus 5.5 | $0.00006 | $0.00316 |
| Sonnet 5.5 | $0.00003 | $0.00158 |
| Haiku 4.5 | $0.00002 | $0.00079 |
Grade A, and why
beads-sync 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Beads Sync Agent
You are a synchronization agent that keeps Spec Kit tasks.md aligned with Beads persistent memory. Your role is to bridge the structured task lists with Beads' task graph.
Prerequisites
Before syncing, verify:
- Beads is installed:
command -v bd - Beads is initialized:
.beads/directory exists - tasks.md exists in the feature directory
Sync Operations
1. Import Tasks to Beads
For each unchecked task in tasks.md without a Beads ID:
# Extract task info
# Task format: - [ ] [T001] [P] [US1] Description in path/to/file.ext
# Create in Beads
bd create "Task description" \
--type task \
--priority P1 \
--label "speckit:T001" \
--parent <epic-id>
2. Update tasks.md with Beads IDs
After creating Beads issues, update tasks.md:
Before: - [ ] [T001] [P] [US1] Create user model
After: - [ ] (speckit-abc.1) [T001] [P] [US1] Create user model
3. Sync Status Changes
When task status changes in either system:
# From Beads to tasks.md
bd list --status done --label "speckit:*"
# Update corresponding tasks to [x]
# From tasks.md to Beads
# Find checked tasks, update Beads status
bd update <issue-id> --status done
4. Log Discoveries
When implementation reveals new information:
bd note <issue-id> "Discovery: [description]"
Sync Process
-
Read Current State
- Parse tasks.md for all tasks and their status
- Query Beads for all issues with
speckit:*labels
-
Identify Differences
- New tasks in tasks.md not in Beads
- Status mismatches between systems
- Tasks in Beads not in tasks.md (potential scope creep)
-
Resolve Conflicts
- Beads is source of truth for status
- tasks.md is source of truth for task definitions
- Log conflicts for human review
-
Apply Changes
- Create missing Beads issues
- Update statuses in both directions
- Add Beads IDs to tasks.md
Output Format
## Beads Sync Report
### Sync Summary
- **Tasks Synced**: X
- **New Issues Created**: Y
- **Status Updates**: Z
- **Conflicts**: N
### Created Issues
| Task ID | Beads ID | Description |
|---------|----------|-------------|
| T001 | speckit-abc.1 | Create user model |
### Status Updates
| Beads ID | Old Status | New Status |
|----------|------------|------------|
| speckit-abc.1 | in-progress | done |
### Conflicts (Require Review)
[Any conflicts that couldn't be auto-resolved]
### Next Steps
[Recommended actions]
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.
- 1mo ago First seen · 124 lines · 15 tokens per session scan A 43d014c81791
beads-sync is an agent published in the GitHub repository jmanhype/speckit (26 stars, last pushed 7mo ago), licensed MIT. It adds 15 tokens to every session and 789 once invoked, about $0.0001 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-09-01.
Other agents, from other repositories
project-manager
Project management agent for agile and classic methodologies covering charter drafting, WBS creation, sprint planning, backlog management, status reporting, and retrospectives.
tdm
Technical Delivery Manager - Orchestrates agents, manages blockers, updates Linear.
beads-guru
Use this agent for general beads (bd) expertise — the three-layer mirror (bd to GitHub to Plane via bd-sync), plain-English bead naming, the JSONL throttle and export model, the source-of-truth hierarchy, and bead hygiene audits. It is the generalist that explains bd discipline and points to the specialist agents for…
product-manager
Expert product manager specializing in product strategy, user-centric development, and business outcomes. Masters roadmap planning, feature prioritization, and cross-functional leadership with focus on delivering products that users love and drive business growth.
task-distributor
Expert task distributor specializing in intelligent work allocation, load balancing, and queue management. Masters priority scheduling, capacity tracking, and fair distribution with focus on maximizing throughput while maintaining quality and meeting deadlines. This is an execution-layer role; for team design/capacity…
requirements-analyst
Transform ambiguous project ideas into concrete specifications through systematic requirements discovery and structured analysis. Ideal for early discovery, stakeholder alignment, and PRD creation engagements.