keen-code: Skill for Claude Code

.agents/skills/release/SKILL.md

release is a skill for Claude Code from mochow13/keen-code. It costs 10 tokens per session (596 once invoked), scanned A, original, MIT.

A set of instructions for releasing a new version of a software project. It covers checking Git tags and commits, choosing a semantic-version change, updating version files, and preparing the changelog.

In plain words
What is it for?
Use it when preparing a project release, reviewing changes since the previous version, updating release metadata, and organizing changelog entries.
Why use it?
It provides a repeatable release checklist and helps avoid forgetting version or changelog updates. Semantic versioning uses major, minor, and patch numbers to describe the kind of change.

Skill for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: installed under .agents/ (shared by several agents).

This is mochow13/keen-code's own configuration. It tells Claude Code how to work on keen-code itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything keen-code configures →

Reuse

Borrowing it

Nothing to install: this file belongs to mochow13/keen-code. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/mochow13/keen-code/main/.agents/skills/release/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/mochow13/keen-code

Made for: Claude Code.

Wrote 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.

agentmods badge for release

README.md
[![agentmods](https://agentmods.dev/badge/skills/mochow13/keen-code/release/github.svg)](https://agentmods.dev/skills/mochow13/keen-code/release)
Your own site
<a href="https://agentmods.dev/skills/mochow13/keen-code/release"><img src="https://agentmods.dev/badge/skills/mochow13/keen-code/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.

agentmods 80×15 button for release

Your own site · 80×15
<a href="https://agentmods.dev/skills/mochow13/keen-code/release"><img src="https://agentmods.dev/badge/skills/mochow13/keen-code/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 10 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 596 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00010 $0.00596
Opus 5.5 $0.00004 $0.00238
Sonnet 5.5 $0.00002 $0.00119
Haiku 4.5 $0.00001 $0.00060

Measured 2mo ago against content hash 03e466060c78, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

.agents/skills/release/SKILL.md · 60 lines

How it starts

The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Release Skill

Target version (optional): $ARGUMENTS

If no target version is provided, inspect the latest release tag and commits since that tag before making any changes. Suggest a semantic-version bump to the user and wait for confirmation:

  • major for intentional breaking changes.
  • minor for backward-compatible features.
  • patch for fixes, documentation, dependencies, and internal changes.

Use git tag --sort=-version:refname to identify the latest version tag and git log <latest-tag>..HEAD --oneline to review subsequent commits. Also consider unreleased changelog entries. State the latest tag, the commits considered, the recommended version, and a concise rationale. If there are no commits since the latest tag, say that no release is recommended.

Once a version is supplied or confirmed, use it as the target version for the remaining steps.

Steps

  1. Bump versions. Update the version string in both files to the target version:

    • cmd/main.go
    • npm/package.json
  2. Update CHANGELOG.md.

    • Move all entries under [Unreleased] into a new [X.Y.Z] - YYYY-MM-DD section below it.
    • Add a new empty [Unreleased] section at the top.
    • Check the commit history for any changes that should be included in the release and were missing in the [Unreleased] section.
    • Update the comparison links at the bottom of the file.
  3. Run the tests.

    go test -race ./...
    
  4. Verify the npm wrapper.

    cd npm && npm pack --dry-run
    
  5. Commit the version bump. Stage only the four changed files and commit:

    • cmd/main.go
    • npm/package.json
    • CHANGELOG.md
  6. Create and push the tag.

    git tag vX.Y.Z && git push origin main && git push origin vX.Y.Z
    

    The tag must match npm/package.json version exactly (e.g. v1.2.3).

  7. Watch the pipelines. Pushing the tag triggers the build and release workflows. Watch them to completion:

    gh run watch $(gh run list --limit 1 --json databaseId --jq '.[0].databaseId')
    

    If a run fails, inspect logs with gh run view <run-id> --log-failed.

Read the full file on GitHub · 60 lines

Changes

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.

  1. 2mo ago First seen · 60 lines · 10 tokens per session scan A 03e466060c78

Subscribe to this mod's changes

release is a skill published in the GitHub repository mochow13/keen-code (75 stars, last pushed yesterday), licensed MIT. It adds 10 tokens to every session and 596 once invoked, about $0.0000 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-30.