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 skills/dollardill/beads-superpowers/document-releasenpx skills add DollarDill/beads-superpowers --skill document-releasegit 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/document-release)<a href="https://agentmods.dev/skills/dollardill/beads-superpowers/document-release"><img src="https://agentmods.dev/badge/skills/dollardill/beads-superpowers/document-release.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.00103 | $0.03429 |
| Opus 5 | $0.00051 | $0.01715 |
| Sonnet 5 | $0.00021 | $0.00686 |
| Haiku 4.5 | $0.00010 | $0.00343 |
Grade A, and why
document-release 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 6d 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 — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Document Release: Post-Ship Documentation Update
Announce at start: "I'm using the document-release skill to audit and update project documentation."
Run after code changes are committed but before PR merge. Ensures all project documentation accurately reflects shipped code.
Beads Integration
# Create a doc-update bead at start
bd create "Docs: update documentation for <branch>" -t chore
Closed with evidence at Step 9 — the single source of truth for the close command.
Key Operating Principles
Automation with guardrails: Make obvious factual corrections automatically (path updates, version numbers, table additions) but pause for subjective decisions (narrative changes, security model updates, large rewrites, version bumps).
Auto-update (apply without asking):
- Factual corrections derived directly from the diff
- Adding items to existing lists and tables
- Updating file paths, counts, and version numbers
- Fixing stale cross-references between documents
- Minor CHANGELOG wording polish (preserving all content)
- Marking TODOs as complete
Always ask before:
- Narrative or philosophy changes
- Removing any section
- Security model rewrites
- Large rewrites (10+ lines in one section)
- VERSION bumps
- New TODO items
Audit Methodology (9-Step Process)
Step 0: Platform Detection
Detect git platform (GitHub/GitLab/unknown) and determine the base branch. Use gh/glab if available, fall back to git-native commands.
Done when: the platform and base branch are both determined.
Step 1: Pre-flight and Diff Analysis
- Verify you are on a feature branch (not base branch)
- Gather what changed:
git diff <base>..HEADandgit log --oneline <base>..HEAD - Discover all
.mdfiles:find . -name '*.md' -not -path './.git/*' -not -path './.worktrees/*' - Categorise changes: new features, behaviour changes, removals, infrastructure
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.
- 6d ago First seen · 208 lines · 103 tokens per session scan A 2d4e22b0327b
document-release is a skill published in the GitHub repository DollarDill/beads-superpowers (26 stars, last pushed 14d ago), licensed MIT. It adds 103 tokens to every session and 3,429 once invoked, about $0.0005 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-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/…
commit
Git commit workflow with precommit hook handling, lint/type checking, README updates, and API reference updates. Use when the user wants to commit changes. Handles precommit hooks that modify files (formatting, linting) by re-staging and retrying. Runs ruff lint and pyright type checks on staged Python files, and…
branch-and-worktree-workflow
Isolates feature work in its own branch or worktree and integrates it cleanly when done. Use this when starting work that should not disturb the current workspace, when several efforts must proceed in parallel on one repository, or when implementation is finished and the change needs merging, rebasing, or splitting…
precommit
Pre-commit checks — lint:fix -> build -> test.
next-step
Change-aware next step advisor. Use when: user asks what to do next, workflow progression is unclear, session just started with dirty worktree. Not for: executing the suggested command (user decides), auto-loop decisions (hooks handle that). Output: findings-based suggestions or session summary with commit seed.
precommit-fast
Quick pre-commit checks — lint:fix -> test.