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 commands/vrennat/developersdevelopers/bootstrapgit clone --depth 1 https://github.com/vrennat/developersDevelopersWhat 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.00061 | $0.01005 |
| Opus 5 | $0.00030 | $0.00502 |
| Sonnet 5 | $0.00012 | $0.00201 |
| Haiku 4.5 | $0.00006 | $0.00101 |
Grade C, and why
bootstrap 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 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf docs/superpowers How it starts
The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/bootstrap
One-time project setup for the developersDevelopers workflow. Probes current state, creates missing directories, prints copy-paste commands for everything else.
Idempotent: safe to re-run. The only filesystem mutations are mkdir docs/specs/ and mkdir docs/plans/. Migration moves, CLAUDE.md edits, and hook installs are printed, not executed — the user runs them when ready.
Procedure
-
Verify cwd is a git repo:
git rev-parse --git-dir. If not, stop and tell user togit initfirst. -
Probe state:
docs/specs/— exists or absentdocs/plans/— exists or absentdocs/superpowers/specs/— legacy obra pathdocs/superpowers/plans/— legacy obra pathCLAUDE.mdat repo root.claude/settings.json(for hook detection)
-
Create what's missing:
mkdir -p docs/specs docs/plans(always safe)
-
Print state report:
=== developersDevelopers /bootstrap ===
Repo: <git remote get-url origin 2>/dev/null || echo "(no remote)">
docs/specs/ <created | already exists>
docs/plans/ <created | already exists>
Legacy paths: <none | docs/superpowers/specs/ (N files), docs/superpowers/plans/ (N files)>
CLAUDE.md: <present | missing>
Hooks: <configured in .claude/settings.json | not configured>
=================================
- If legacy paths detected, print migration commands (do NOT execute):
To migrate legacy obra/superpowers paths to the new convention:
git mv docs/superpowers/specs/*.md docs/specs/ 2>/dev/null
git mv docs/superpowers/plans/*.md docs/plans/ 2>/dev/null
rm -rf docs/superpowers
git add -A
git commit -m "refactor: migrate spec/plan paths to docs/specs and docs/plans"
Review and run when ready.
- If CLAUDE.md is missing or doesn't reference this plugin, print a snippet:
Consider adding to CLAUDE.md:
## Workflow
This project uses developersDevelopers (github.com/vrennat/developersDevelopers).
- /brainstorm <idea> -> spec at docs/specs/
- /impl <input> -> classified, routed execution
- /research <q> -> measurable experiments
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 · 108 lines · 61 tokens per session scan C 81e0f520bf4e
bootstrap is a command published in the GitHub repository vrennat/developersDevelopers (2 stars, last pushed 1mo ago), licensed MIT. It adds 61 tokens to every session and 1,005 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-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.