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 skills add DollarDill/beads-superpowers --skill project-initgit clone --depth 1 https://github.com/DollarDill/beads-superpowersWrote 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/dollardill/beads-superpowers/project-init)<a href="https://agentmods.dev/skills/dollardill/beads-superpowers/project-init"><img src="https://agentmods.dev/badge/skills/dollardill/beads-superpowers/project-init.svg" alt="Measured on agentmods" 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.00052 | $0.03226 |
| Opus 5 | $0.00026 | $0.01613 |
| Sonnet 5 | $0.00010 | $0.00645 |
| Haiku 4.5 | $0.00005 | $0.00323 |
Grade C, and why
project-init scanned grade C with 1 finding 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 7d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf .beads/ How it starts
The opening of the file, as written. The whole thing — 298 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Init: Beads/Dolt Database Setup and Recovery
Announce at start: "I'm using the project-init skill to set up or recover the beads database."
Iron Law: NEVER Run bd init --force
NEVER run bd init --force (deprecated in v1.0.4). Use the named-intent alternatives: bd init --reinit-local (preserves remote) or bd init --discard-remote (explicit destruction).
Why: Issue #2363 documents an AI agent that destroyed 247 issues via bd init --force cascade. The root cause was misdiagnosing "server can't connect" as "database missing". bd init --force is a nuclear option that should ONLY be run by a human who explicitly types it.
This Iron Law is the Production-Grade Doctrine applied to your data ledger: never take the shortcut that accepts catastrophic, irreversible risk.
| Action | Safe? | Use When |
|---|---|---|
bd init |
✅ Safe | Fresh project, no existing .beads/ |
bd bootstrap |
✅ Safe | Cloned repo with remote beads data |
bd doctor --fix --yes |
✅ Safe | Database exists but seems broken |
bd init --force |
❌ NEVER | Deprecated (v1.0.4) — do NOT use |
bd init --reinit-local |
⚠️ Recovery only | Reinitialize local state, preserve remote data |
bd init --discard-remote |
⚠️ Recovery only | Discard remote data and reinitialize (explicit destruction) |
Diagnostic Phase (Always Run First)
Before taking ANY action, run diagnostics to understand the current state:
bash scripts/diagnose.sh
One Bash call gathers the full read-only battery as labeled RAW DATA (no verdicts, no
fixes): bd/dolt versions, .beads/ presence, config.yaml/metadata.json, whether
bd list/bd vc status work, and any dolt refs on the git remote. Read the == section ==
output, then author the diagnosis yourself against the Decision Matrix below:
Diagnosis: Path: <A/B/C/D/E/F, from the Decision Matrix>
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 298 lines · 52 tokens per session scan C f3efa312615e
project-init is a skill published in the GitHub repository DollarDill/beads-superpowers (26 stars, last pushed 15d ago), licensed MIT. It adds 52 tokens to every session and 3,226 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
beads-onboard
This skill should be used when the user asks to "onboard beads", "set up beads conventions", "configure beads for this project", "set up project labels", "improve my beads quality", "run beads onboard", "upgrade beads conventions", "re-run beads onboard", or when a project has .beads/ but no .beads/conventions/…
lineage
Use when user invokes /lineage with a column name (optionally qualified with table/schema). Also triggers on "trace this column", "where does X come from", "what reads from Y table". Traces column-level data lineage through SQL, Kafka, Spark, JDBC, and ORM codebases. Produces a structured lineage path with confidence…
bv
Beads Viewer - Graph-aware triage engine for Beads projects. Computes PageRank, betweenness, critical path, and cycles. Use --robot- flags for AI agents.
using-herdr-sibling-panes
Use when inside herdr (HERDRENV=1), the current pane is acting as the orchestrator for the task, and idle sibling agent panes can take delegated work — operational repo tasks standalone, or any routed task as the delegation transport for the orchestration skill.
shipyard-executing-plans
Use when you have a written implementation plan to execute, either in the current session with builder/reviewer agents or in a separate session with review checkpoints. Also use when the user says "build this", "implement this", "execute the plan", "run the plan", or when a plan file has been loaded with independent…
import-spec
Import a spec-kit feature spec into Shipyard, replacing brainstorming. Use when a spec-kit feature directory exists with spec.md.