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 RockyHong/super-bootstrap --skill releasegit clone --depth 1 https://github.com/RockyHong/super-bootstrapWrote 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/rockyhong/super-bootstrap/release)<a href="https://agentmods.dev/skills/rockyhong/super-bootstrap/release"><img src="https://agentmods.dev/badge/skills/rockyhong/super-bootstrap/release/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/rockyhong/super-bootstrap/release"><img src="https://agentmods.dev/badge/skills/rockyhong/super-bootstrap/release.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.00024 | $0.01579 |
| Opus 5.5 | $0.00010 | $0.00632 |
| Sonnet 5.5 | $0.00005 | $0.00316 |
| Haiku 4.5 | $0.00002 | $0.00158 |
Grade A, and why
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 22d 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release
Project Config
- Type: generic (Claude Code plugin / marketplace)
- Version file (single source of truth):
plugins/super-bootstrap/.claude-plugin/plugin.json→version(marketplace.jsoncarries noversion)
- Derived manifest mirror:
.claude-plugin/marketplace.json→plugins[0].description(synced fromplugin.jsonat release; direct edits get overwritten)
- Platforms: none (single artifact)
- Main branch: main
Protocol
Code blocks below are POSIX bash — on a PowerShell-primary device, run them via the Bash tool; if porting to PowerShell, rewrite in its idiom and single-quote git's caret/brace revisions (git rev-parse 'v1.2.3^{commit}').
1. Qualify
Run in parallel:
git status— working tree must be clean. If dirty, stop: "Commit or stash changes first."git branch --show-current— must be onmain. If not, warn and ask to continue.
1.5 Dispatch-shell pre-flight (warn, not block)
Scan plugins/*/skills/*/SKILL.md for bounded-judgment verbs — classify, rank, scan, digest (case-insensitive) — appearing in the skill's protocol/execution body. For each hit, check whether that skill dispatches a typed agent (a sibling agents/<name>.md, or a subagent_type: / "dispatch the ... agent" reference in the same file). A skill frontmatter alone can't pin a model — bounded judgment left inline runs unpinned, at the gateway's tier.
Skip skills whose row in plugins/super-bootstrap/README.md § "Inline vs Dispatch" documents an inline rationale — those are decided placements, not misses; warning on them every release trains the reader to ignore the check.
Bounded-judgment verb(s) found, no agent dispatch, and no documented inline rationale → warn, one line, don't block:
⚠ dispatch-shell check: {file} — bounded-judgment verb(s) ({verbs}) with no agent dispatch. Consider splitting into dispatch-shell + typed agent (see
skills/triage+agents/triage.md).
List every matching file on one line if more than one hits. Never halts the release — this is a nudge surfaced in the release report, not a qualify gate.
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.
- 22d ago Changed 5d67cc2955c4
- 1mo ago First seen · 138 lines · 24 tokens per session scan A ae72bf6926b9
release is a skill published in the GitHub repository RockyHong/super-bootstrap (3 stars, last pushed 9d ago), licensed MIT. It adds 24 tokens to every session and 1,579 once invoked, about $0.0001 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-08-31.
Other skills, from other repositories
qector-release-engineering
QECTOR release engineering, wheel-only distribution, the chunked base64 Rust-core delivery, feature flags in published wheels, the pre-flight gates, and the v2 token format. Load for any question about packaging, building, releasing, the RUSTSRCB64 secrets bundle, the promotion of a Provisional symbol to stable, or…
release
CONTRIBUTOR TOOL - Cut a plugin release: bump plugin.json version, finalize CHANGELOG, update README if needed, gate on make ci, commit, tag vX.Y.Z, and create the GitHub release. Use when shipping a new plugin version. NOT distributed.
ln-62-release-publisher
Prepares and publishes an explicitly requested tagged GitHub release; does not deploy applications.
release
Bump a plugin's version, write a detailed changelog entry for the upgrade skill to consume, and commit+push. Takes a plugin slug argument identifying which plugin under plugins/ to release. Use this skill whenever the user says "release", "version bump", "cut a release", "changelog and push", or finishes a set of…
release
Bump a plugin's version, write a detailed changelog entry for the upgrade skill to consume, and commit+push. Takes a plugin slug argument identifying which plugin under plugins/ to release. Use this skill whenever the user says "release", "version bump", "cut a release", "changelog and push", or finishes a set of…
pre-release-review
Run the pre-release gate for this multi-plugin monorepo: establish each plugin's release boundary from its last reachable tag to HEAD, audit every changed plugin's [Unreleased] changelog against the actual code diff, identify contract-surface and breaking changes, and, per the objective the user picks up front, either…