Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/hanamizuki/solopreneurnpx agentmods add skills/hanamizuki/solopreneur/releaseWrote 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/hanamizuki/solopreneur/release)<a href="https://agentmods.dev/skills/hanamizuki/solopreneur/release"><img src="https://agentmods.dev/badge/skills/hanamizuki/solopreneur/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/hanamizuki/solopreneur/release"><img src="https://agentmods.dev/badge/skills/hanamizuki/solopreneur/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00205 | $0.05462 |
| Opus 5 | $0.00102 | $0.02731 |
| Sonnet 5 | $0.00041 | $0.01092 |
| Haiku 4.5 | $0.00020 | $0.00546 |
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 9d 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 — 495 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release
Manual release flow for the solopreneur multi-plugin marketplace.
Implements the release rule documented in CLAUDE.md at the repo root.
This skill is interactive. Confirm each decision with the user. Do not autopilot version bumps or release publishing.
Pre-flight
-
Confirm cwd is the repo root or a worktree of it. Run from the directory containing
.claude-plugin/marketplace.json,skills/, andsrc/. -
Confirm working tree is clean:
git status --porcelainIf unclean, stop and ask the user to commit or stash first. Don't release on top of uncommitted work. The new commit's content depends on the working tree.
-
Confirm we're on
main(the typical release path is "merge → release"):git branch --show-currentIf not on main, ask the user to confirm the branch is intentional.
-
Pull latest:
git fetch origin && git pull --ff-onlyIf
--ff-onlyfails (local has commits), stop and ask the user.
Step 1: Detect per-plugin changes since last tag
For each sub-plugin, find its last <plugin>--v* tag and compare against HEAD.
Plugin names match the first-level directory names under both canonical roots.
PLUGINS=(solopreneur designer marketer ios-dev android-dev ai-engineer neo4j-dev)
for p in "${PLUGINS[@]}"; do
LAST_TAG=$(git tag -l "${p}--v*" --sort=-v:refname | head -1)
# Transitional fallback: the v0.5.x → v0.5.3 rename dropped the `solo-`
# prefix from sub-plugins. The first /release run after that rename has
# no `<bare>--v*` tag yet, so look for the legacy `solo-<bare>--v*` tag
# to avoid a misleading "NO TAG YET" message. Once the new tag exists,
# this fallback never fires again.
if [ -z "$LAST_TAG" ] && [ "$p" != "solopreneur" ]; then
LAST_TAG=$(git tag -l "solo-${p}--v*" --sort=-v:refname | head -1)
fi
if [ -z "$LAST_TAG" ]; then
echo "=== $p: NO TAG YET (first release) ==="
git log --oneline -- "skills/$p/" "src/$p/"
continue
fi
CHANGED=$(git diff --name-only "$LAST_TAG"..HEAD -- "skills/$p/" "src/$p/" | wc -l | tr -d ' ')
if [ "$CHANGED" -gt 0 ]; then
echo "=== $p: $CHANGED files changed since $LAST_TAG ==="
git log --oneline "$LAST_TAG"..HEAD -- "skills/$p/" "src/$p/"
else
echo "=== $p: no changes since $LAST_TAG ==="
fi
done
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.
- 9d ago First seen · 495 lines · 205 tokens per session scan A 59282b5b9ec7
release is a skill published in the GitHub repository hanamizuki/solopreneur (148 stars, last pushed 23d ago), licensed MIT. It adds 205 tokens to every session and 5,462 once invoked, about $0.0010 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
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".
updater_guide
Guidance for checking for and installing Row-Bot updates.