agentmods.dev

release

Release instructions for the succinctly Rust package, covering change review, testing, version updates, snapshots, and the automated publishing process.

In plain words
What is it for?
Use them to prepare a new version, review changes since the last release, run builds and tests, update snapshots, and let CI publish the package.
Why use it?
They reduce release mistakes by making the required checks and versioning steps explicit.

Skill for Claude CodeCodex

51 2d ago A scan 0 tokens original MIT
View the source file rust-works/succinctly
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/rust-works/succinctly/release
Any agent
npx skills add rust-works/succinctly --skill release
Clone the repo
git clone --depth 1 https://github.com/rust-works/succinctly

Made for: Claude Code, Codex.

Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 953 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.00000 $0.00953
Opus 5 $0.00000 $0.00477
Sonnet 5 $0.00000 $0.00191
Haiku 4.5 $0.00000 $0.00095

Measured 2d ago against content hash fb4924629ad7, 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 2d 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.

.claude/skills/release/SKILL.md · 105 lines

How it starts

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

Release Skill

Creates releases for the succinctly crate. Triggered by terms like "release", "publish", "new version".

Release Process

IMPORTANT: Do NOT run cargo publish manually. The CI workflow handles crates.io publishing automatically after building binaries for all platforms.

Steps

  1. Gather ALL changes since last release

    git describe --tags --abbrev=0  # Get last tag (e.g., v0.4.0)
git log v0.4.0..HEAD --oneline --no-merges  # ALL commits, not just recent
    • Review the FULL list - there may be 50+ commits
    • Categorize by: CLI, Performance, Memory, SIMD, Compatibility, Fixes

  2. Run quality checks FIRST

    ./scripts/build.sh
cargo test --all-features

  3. Bump version in Cargo.toml

    • Follow semver: MAJOR.MINOR.PATCH
    • MAJOR: Breaking API changes
    • MINOR: New features (backward compatible)
    • PATCH: Bug fixes (backward compatible)
    • Run cargo check or cargo build to update Cargo.lock with the new version

  4. Update version snapshot (ALWAYS required)

    grep -r "0\.4\.0" tests/snapshots/  # Find version in snapshots
    • Update tests/snapshots/cli_golden_tests__version.snap
    • This test WILL fail if you skip this step

  5. Update CHANGELOG.md

    • Create new version section with date YYYY-MM-DD
    • Group changes by user impact (not by commit type):
      • CLI Enhancements - user-facing CLI features
      • Performance - speed/memory improvements with metrics
      • SIMD Optimizations - architecture-specific speedups
      • Memory Optimizations - space efficiency improvements
      • Fixed - bug fixes
    • Update comparison links at bottom of file

  6. Commit the release

    git add Cargo.toml Cargo.lock CHANGELOG.md tests/snapshots/
git commit -m "chore(release): prepare vX.Y.Z"

  7. Push via PR (branch protection may block direct push)

    git checkout -b release/vX.Y.Z
git push -u origin release/vX.Y.Z
gh pr create --title "chore(release): prepare vX.Y.Z" --body "..."
    • If direct push to main is allowed, use that instead
    • Wait for PR to be merged before tagging

Read the full file on GitHub · 105 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. 2d ago First seen · 105 lines · 0 tokens per session scan A fb4924629ad7

Subscribe to this mod's changes

release is a skill published in the GitHub repository rust-works/succinctly (51 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 953 tokens. 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.

Code reviewGit and workflowTesting
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens