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 avivsinai/shaon --skill releasegit clone --depth 1 https://github.com/avivsinai/shaonWrote 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/avivsinai/shaon/release)<a href="https://agentmods.dev/skills/avivsinai/shaon/release"><img src="https://agentmods.dev/badge/skills/avivsinai/shaon/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.00030 | $0.00377 |
| Opus 5 | $0.00015 | $0.00188 |
| Sonnet 5 | $0.00006 | $0.00075 |
| Haiku 4.5 | $0.00003 | $0.00038 |
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 7d 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.
What it actually says
Release Workflow
Run this skill with: /release $ARGUMENTS
$ARGUMENTS should be the new version number (e.g., 0.4.0). If not provided, ask the user.
Steps
-
Validate version: Confirm
$ARGUMENTSis a valid semver (MAJOR.MINOR.PATCH). Read current version fromCargo.toml. -
Bump Cargo.toml: Update
version = "..."in[package]section. -
Bump plugin.json: Update
"version": "..."in.claude-plugin/plugin.json. -
Update README.md: Replace any occurrences of the old version string with the new version (e.g., in install commands, badges, or header).
-
Build release binary: Run
cargo build --releaseand confirm it compiles cleanly. -
Run clippy: Run
cargo clippy -- -D warningsto ensure no lint issues. -
Show diff: Run
git diffand present the changes for review. -
Commit: Create a single commit:
Release v{VERSION}with the version-bumped files. -
Tag: Create an annotated git tag:
git tag -a v{VERSION} -m "Release v{VERSION}". -
Report: Print the new version, tagged commit hash, and cached binary path (
~/.cache/shaon/{VERSION}/shaon). Remind the user togit push --follow-tagswhen ready.
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.
- 7d ago First seen · 34 lines · 30 tokens per session scan A 986476038380
release is a skill published in the GitHub repository avivsinai/shaon (2 stars, last pushed yesterday), licensed MIT. It adds 30 tokens to every session and 377 once invoked, about $0.0002 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-31.
Other skills, from other repositories
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
gh-credit-harvest
Harvest one community PR into a release branch with authorship and credit preserved, verified green, and a warm thank-you.
release
Skill "release" from Hmbown/Codewhale, covering release, invocation, non-goals and workflow.
github
GitHub CLI (gh) for repository management, issues, pull requests, releases, workflows, search, gists, and API access. Use when the user asks about any GitHub operation — creating repos, forking, cloning, PR workflows, issue triage, CI/CD runs, code search, release management, or direct API calls. Keywords: github, gh…
git
Run git version control commands for repository management. Use when the user asks to check status, view history or diffs, stage and commit changes, manage branches, merge or rebase, work with remotes, stash changes, tag releases, cherry-pick commits, bisect regressions, resolve conflicts, manage worktrees or…
cw-gates
Use before claiming any Codewhale change is done, green, or ready to land: the focused-to-broad verification ladder, the budget checks CI enforces, and the rules for what counts as a passing test.