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 release-initgit 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-init)<a href="https://agentmods.dev/skills/rockyhong/super-bootstrap/release-init"><img src="https://agentmods.dev/badge/skills/rockyhong/super-bootstrap/release-init/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-init"><img src="https://agentmods.dev/badge/skills/rockyhong/super-bootstrap/release-init.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.00025 | $0.01456 |
| Opus 5.5 | $0.00010 | $0.00582 |
| Sonnet 5.5 | $0.00005 | $0.00291 |
| Haiku 4.5 | $0.00003 | $0.00146 |
Grade A, and why
release-init 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Init
Protocol
1. Check for existing project skill
Look for .claude/skills/release/SKILL.md in the repo root.
If it exists, ask:
Project release skill already exists. Overwrite with fresh detection? (y/n)
Stop if user declines.
2. Detect project type
Scan the working directory. First match wins:
| Marker | Type |
|---|---|
ProjectSettings/ProjectSettings.asset (search recursively) |
unity |
package.json + src-tauri/ directory |
tauri |
package.json |
node |
*.xcodeproj or *.xcworkspace (in root) |
ios-native |
build.gradle or build.gradle.kts (in root) |
android-native |
| None of the above | generic |
3. Discover version files and current values
Read current version values from the detected files:
unity:
- Find
ProjectSettings/ProjectSettings.asset(may be nested, e.g.ProjectName/ProjectSettings/) - Read:
bundleVersion(display version),AndroidBundleVersionCode,buildNumber.iPhone - Report all three values
tauri:
package.json→versionsrc-tauri/tauri.conf.json→versionsrc-tauri/Cargo.toml→version
node:
package.json→version
ios-native:
- Find
Info.plist→CFBundleShortVersionString,CFBundleVersion
android-native:
build.gradleorbuild.gradle.kts→versionName,versionCode
generic:
- Ask user: "Where does your version live? (file path and field name)"
4. Detect platforms and recommend tagging approach
Determine if multi-platform based on project type and evidence:
| Type | Signal | Recommendation |
|---|---|---|
unity |
Has both Android + iOS build settings in ProjectSettings | Multi-platform: android, ios |
unity |
Only one platform target | Single platform, no platform tags |
tauri |
Desktop app | Single artifact, no platform tags |
node |
Web app / server | Single deploy, no platform tags |
ios-native |
iOS only | Single platform, no platform tags |
android-native |
Android only | Single platform, no platform tags |
What ships with it
1 file 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.
- 1mo ago First seen · 160 lines · 25 tokens per session scan A 79b186cf7f1d
release-init is a skill published in the GitHub repository RockyHong/super-bootstrap (3 stars, last pushed 10d ago), licensed MIT. It adds 25 tokens to every session and 1,456 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
git-workflow
Git branching, commit conventions, rebase vs merge, conflict resolution, and release tagging. Use when setting up a git workflow, writing commits, resolving conflicts, or preparing a release.
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…
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…