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/jketreno/clare/releasenpx skills add jketreno/clare --skill releasegit clone --depth 1 https://github.com/jketreno/clareWrote 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/jketreno/clare/release)<a href="https://agentmods.dev/skills/jketreno/clare/release"><img src="https://agentmods.dev/badge/skills/jketreno/clare/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 | $0.00029 | $0.00855 |
| Opus 5 | $0.00015 | $0.00428 |
| Sonnet 5 | $0.00006 | $0.00171 |
| Haiku 4.5 | $0.00003 | $0.00085 |
Grade A, and why
release scanned grade A with 1 finding 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 5d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -fsSLO https://github.com/jketreno/clare/releases/download/vX.Y.Z/clare-installer-vX.Y.Z.sh How it starts
The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLARE Repo Skill: Prepare a Release
Use this skill when a user asks to prepare or cut a release for this repository. This skill does not publish the release directly.
Non-negotiables
- Git tree must be clean before starting.
- Release must run from
main. ./clare/verify-ci.shmust pass before handoff.- Before release prep, audit docs for command/flag accuracy by inspecting scripts.
- If docs and implementation disagree, abort prep and report a mismatch summary.
- Update release collateral, then stage, commit, and push before handoff.
- Do not run
./scripts/release.shautomatically because signing requires manual passphrase entry. - Update README release version block by replacing only the content between:
<!-- RELEASE_VERSION_START --><!-- RELEASE_VERSION_END -->
- The updated block must include:
- the new version label
vX.Y.Z - a link to
https://github.com/jketreno/clare/releases/tag/vX.Y.Z - install commands with exact installer filename for that version
- the new version label
Phase 1: Preflight + Accuracy Audit
Run:
git status --porcelain
git branch --show-current
./clare/verify-ci.sh
Inspect script capabilities and compare with README/docs references:
./scripts/release.sh --help
./scripts/clare-installer.sh --help
Verify README and all files under docs/ only reference supported commands and flags.
Abort criteria:
- Any command in README/docs uses unsupported script flags
- Any release instructions refer to removed scripts
- Any required prerequisites are outdated or missing
If aborting, provide a concise mismatch summary with file paths and exact incorrect command snippets.
Phase 2: Changelog Update
Determine the release baseline:
LAST_TAG="$(git tag -l 'v*' --sort=-version:refname --merged HEAD | head -1)"
If LAST_TAG exists, summarize user-relevant changes from LAST_TAG..HEAD.
If no tag exists, summarize user-relevant changes from repo start.
Update CHANGELOG.md with:
- new release heading
vX.Y.Z - concise user-facing summary of features/fixes/behavior changes
- no internal-only noise unless it affects users
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.
- 5d ago First seen · 118 lines · 29 tokens per session scan A f0ab7ded9a86
release is a skill published in the GitHub repository jketreno/clare (5 stars, last pushed 1mo ago), licensed MIT. It adds 29 tokens to every session and 855 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
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.
release
Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.
changelog
Create changelog files for important commits in a PR.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
refresh-arm-sdk-release
WORKFLOW SKILL — Prepares Azure.ResourceManager SDK refresh pull requests in azure-sdk-for-net. WHEN: "prepare sdk refresh", "refresh Azure.ResourceManager package", "update ARM SDK from autorest tag", "refresh changelog dependencies". INVOKES: git and GitHub pull request tools for branch, commit, push, and PR…