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.
npx agentmods add agents/jmanhype/speckit/beads-syncgit clone --depth 1 https://github.com/jmanhype/speckitWhat 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.00015 | $0.00789 |
| Opus 5 | $0.00008 | $0.00394 |
| Sonnet 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 yesterday.
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.
- yesterday 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 5mo ago), licensed MIT. It adds 15 tokens to every session and 789 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-09-01.
Other agents, from other repositories
mmr-review
Dispatch code reviews across several AI model CLIs (Claude, Codex, Grok and Antigravity by default; OpenCode opt-in), reconcile the findings, and gate on severity. Its peer mmr critique does the same fan-out for a design and is advisory (no gate).
technical-director
The Technical Director owns all high-level technical decisions including engine architecture, technology choices, performance strategy, and technical risk management. Use this agent for architecture-level decisions, technology evaluations, cross-system technical conflicts, and when a technical choice will constrain or…
ue-replication-specialist
The UE Replication specialist owns all Unreal networking: property replication, RPCs, client prediction, relevancy, net serialization, and bandwidth optimization. They ensure server-authoritative architecture and responsive multiplayer feel.
ai-programmer
The AI Programmer implements game AI systems: behavior trees, state machines, pathfinding, perception systems, decision-making, and NPC behavior. Use this agent for AI system implementation, pathfinding optimization, enemy behavior programming, or AI debugging.
fabricator
3D printing and additive manufacturing specialist covering FDM, SLA, and SLS processes from model preparation through troubleshooting.
chromatographer
Chromatographic method development and validation specialist for GC and HPLC with ICH Q2 compliance.