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/skills/beads-integration/SKILL.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/skills/jmanhype/speckit/beads-integration)<a href="https://agentmods.dev/skills/jmanhype/speckit/beads-integration"><img src="https://agentmods.dev/badge/skills/jmanhype/speckit/beads-integration/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/jmanhype/speckit/beads-integration"><img src="https://agentmods.dev/badge/skills/jmanhype/speckit/beads-integration.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.00043 | $0.01156 |
| Opus 5.5 | $0.00017 | $0.00462 |
| Sonnet 5.5 | $0.00009 | $0.00231 |
| Haiku 4.5 | $0.00004 | $0.00116 |
Grade A, and why
beads-integration 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 — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Beads Integration Skill
You are assisting with a project that uses Beads - a persistent task memory system that survives context limits and session boundaries.
What is Beads?
Beads provides:
- Persistent memory across Claude Code sessions
- Task graph with dependencies and status
- Discovery tracking for implementation insights
- Context preservation before compaction
Core Commands
Initialize Beads
bd init # Initialize in project
bd doctor # Verify setup
Prime Context
bd prime # Load task graph into context
This runs automatically at SessionStart and PreCompact via hooks.
Task Management
bd create "Task description" --type task --priority P1 --label "speckit:T001"
bd list # List all issues
bd list --status todo # Filter by status
bd ready # Show tasks ready to work
bd update <id> --status in-progress
bd update <id> --status done
bd note <id> "Discovery note"
Query Tasks
bd show <id> # Show task details
bd find "search term" # Search tasks
bd list --label "speckit:*" # Find Spec Kit tasks
Pivotal-Style Workflow
Spec Kit + Beads implements Pivotal Labs methodology:
| Pivotal Concept | Beads Implementation |
|---|---|
| Story Types | --type epic/task/bug |
| Story States | --status todo/in-progress/done |
| Dependencies | bd dep add (P0 → P1 → P2) |
| Acceptance Criteria | Epic description field |
Sync Patterns
spec.md + plan.md → Beads Epic
After /speckit.plan, create a Pivotal-style epic:
./.specify/scripts/bash/create-beads-epic.sh specs/001-feature P0
This extracts from spec.md and plan.md:
- Problem Statement
- Business Value
- Architectural Vision
- Integration Tests
- Acceptance Criteria
Epic ID is saved to specs/001-feature/.beads-epic-id
tasks.md → Beads Tasks
After /speckit.tasks, bulk import with dependencies:
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 · 177 lines · 43 tokens per session scan A 65b01659797f
beads-integration is a skill published in the GitHub repository jmanhype/speckit (26 stars, last pushed 7mo ago), licensed MIT. It adds 43 tokens to every session and 1,156 once invoked, about $0.0002 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 skills, from other repositories
work-beads
Use for /work-beads, a requested Beads backlog batch, or implementation of named bead IDs.
continuous-improvement
Capture learnings after tasks. Triggers on task completion, repeated mistakes, retrospective requests, or "what did I learn".
beads
Use when working in a repository that uses bd or Beads for durable project task tracking, issue dependencies, blocker management, multi-session handoff, or shared work memory. Trigger when the user asks to find ready work, claim or close tasks, create follow-up work, inspect blockers, recover project context, or…
mempalace-task
Create, hand off, claim, execute, and close agent tasks through the MemPalace logstream. Use when the user wants to delegate work, prepare a ready-to-paste task for another agent, receive a MemPalace task id, or explicitly launch a supported headless agent in controlled mode.
knowledge-meeting-ingest
Ingest meeting transcripts from any recorder into Knowledge with attendee enrichment, timeline merge, supported decisions and commitments, and verification of substance and sequence. Summary-only input is not a verified meeting ingestion.
knowledge-automation
Create scheduled Knowledge ingestion automations with a verified worker, private-vault authority, and an end-to-end scheduled run. Use when asked to schedule or repair recurring ingestion from any source.