agentmods.dev

release

A release procedure for publishing a new version of structcli, a command-line software library.

In plain words
What is it for?
Use it when preparing a release, including checking changes since the last version, identifying breaking changes, updating release notes, and creating the new tag.
Why use it?
It guides the version choice, changelog, checks, commit, push, and tag steps so releases follow a repeatable process.

Skill for Claude CodeCodex

18 1mo ago A scan 54 tokens original MIT
View the source file leodido/structcli
Install

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.

agentmods
npx agentmods add skills/leodido/structcli/release
Any agent
npx skills add leodido/structcli --skill release
Clone the repo
git clone --depth 1 https://github.com/leodido/structcli

Made for: Claude Code, Codex.

Per session 54 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 817 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00054 $0.00817
Opus 5 $0.00027 $0.00409
Sonnet 5 $0.00011 $0.00163
Haiku 4.5 $0.00005 $0.00082

Measured yesterday against content hash d200167e2e7c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 yesterday.

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.

.skills/release/SKILL.md · 62 lines

How it starts

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

Release structcli

Prerequisites

  • You are on main with a clean working tree.
  • Verify you can push to origin main (check git config user.email against GitHub email privacy settings if pushes are rejected).
  • All CI workflows (testing, wasm) are green on main.

Steps

1. Determine the version

Identify the next version from git tag --sort=-v:refname | head -1 and the nature of changes since the last tag (git log <last-tag>..HEAD --oneline). Look for feat!: or refactor!: prefixes indicating breaking changes.

2. Write the changelog

Gather merged PRs since the last tag. Each commit on main corresponds to a rebase-merged PR. Use the GitHub API to read PR titles, bodies, and labels.

Write the [Unreleased] section in CHANGELOG.md following Keep a Changelog format with these subsections as needed: Added, Changed, Removed, Fixed. Prefix breaking items in Changed with **Breaking:**.

Then:

  • Rename [Unreleased] to [X.Y.Z] - YYYY-MM-DD
  • Add a new empty [Unreleased] section above it
  • Update comparison links at the bottom of the file
  • Commit directly to main: git commit -m "docs(changelog): add vX.Y.Z release notes"
  • Push to main

3. Check for pending release process improvements

If there are Makefile or CI changes needed for the release process itself, open a PR with a chore: prefix (excluded from release notes by .github/release.yml). Wait for merge before proceeding.

4. Release

git checkout main && git pull origin main
make release VERSION=X.Y.Z

The Makefile target:

  1. Guards: clean tree, on main
  2. Bumps const Version in version.go
  3. Regenerates examples/full/ (SKILL.md, llms.txt, AGENTS.md via go generate)
  4. Bumps github.com/leodido/structcli version in all example go.mod files
  5. Commits, tags vX.Y.Z, pushes main + tag

5. Verify

All three must pass:

  1. releasing CI workflow — triggered by the tag push. Runs version-check (verifies version.go matches tag) then goreleaser (creates GitHub Release with auto-generated notes from PR labels).
  2. GitHub Release — exists at https://github.com/leodido/structcli/releases/tag/vX.Y.Z. Auto-generated notes categorize PRs by label: breaking-change → "Breaking Changes", enhancement → "Features & Enhancements", bug → "Bug Fixes", documentation → "Documentation". The chore label is excluded.
  3. Go module proxy — go list -m github.com/leodido/[email protected] resolves. May take a few minutes.

Read the full file on GitHub · 62 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. yesterday First seen · 62 lines · 54 tokens per session scan A d200167e2e7c

Subscribe to this mod's changes

release is a skill published in the GitHub repository leodido/structcli (18 stars, last pushed 1mo ago), licensed MIT. It adds 54 tokens to every session and 817 once invoked, about $0.0003 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.

Git and workflowProductivityclicobraconfiguration-filesenvironment-variablesflagsviper
Related

Other skills, from other repositories

golang-cli-cobra-viper

Building production-quality CLI tools with Cobra command framework and Viper configuration management.

bobmatnyc/claude-mpm-skills · 22 tokens

golang-cli-cobra-viper

Building production-quality CLI tools with Cobra command framework and Viper configuration management.

castle-x/skills-x · 22 tokens

featurevisor

Author, query, and integrate Featurevisor — Git-based feature flags, A/B experiments, and remote config. Use whenever the user mentions Featurevisor, works in a project containing featurevisor.config.js, edits files under attributes/, segments/, features/, variables/, groups/, schemas/, targets/, sets/, or tests/…

featurevisor/featurevisor · 266 tokens

lade

Use Lade safely with coding agents. Use when a project has lade.yml, commands need secrets or temporary network access, or the user mentions Lade, LADE, phonetic spellings like AD/AID/LAID, hooks, lade inject, preToolUse, or agent secret handling.

zifeo/lade · 60 tokens

lade-release

Prepare a Lade release: update CHANGELOG.md and bump crate versions with cargo set-version. Use when cutting a release, tagging vX.Y.Z, publishing to GitHub Releases, or finalizing the changelog before a version bump.

zifeo/lade · 50 tokens

authoring-schemas

Author a mache projection schema (Topology→Node→Leaf) that maps structured data or source code into a filesystem/graph. Use when creating or debugging a -schema.json for a new data source (SQLite/JSON) or a new source language. Covers both dialects — tree-sitter S-expression selectors for code, and JSONPath selectors…

agentic-research/mache · 111 tokens