agentmods.dev

release

A set of instructions for preparing or carrying out a software release. A release is a published version of a project made available to users.

In plain words
What is it for?
Use it to inspect changes since the last tag, choose a version, update release notes, prepare a changelog, or run the release script.
Why use it?
It helps keep version numbers, change logs, tags, and release-related commits consistent.

Skill for Claude CodeCodex

15 14d ago A scan 52 tokens original MIT
View the source file tyql688/sessionview
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/tyql688/sessionview/release
Any agent
npx skills add tyql688/sessionview --skill release
Clone the repo
git clone --depth 1 https://github.com/tyql688/sessionview

Made for: Claude Code, Codex.

Per session 52 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 984 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.00052 $0.00984
Opus 5 $0.00026 $0.00492
Sonnet 5 $0.00010 $0.00197
Haiku 4.5 $0.00005 $0.00098

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

.agent/skills/release/SKILL.md · 96 lines

How it starts

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

Release

Use this skill to choose the release version, prepare CHANGELOG.md, and run scripts/release.sh.

Changelog

  • Write CHANGELOG.md in English.
  • Keep entries user-facing and concise.
  • Prefer sections in this order: ### Added, ### Changed, ### Fixed, ### Removed.
  • Use ### Removed for user-visible removals, dropped support, or deleted workflows.
  • Append a PR number (#N) only if it already appears in commit history; otherwise use a short commit hash (abc1234) only when it adds traceability.
  • Exclude pure CI churn, dependency-only maintenance, test-only changes, formatting-only changes, and dead-code cleanup unless they affect users or release behavior.
  • Keep the active heading as ## [X.Y.Z] - Unreleased while preparing the release. scripts/release.sh stamps the final date.

Commits

  • Use Conventional Commits for every release-related commit.
  • Format commit messages as <type>[optional scope]: <description>, for example docs: update changelog for v0.6.0.
  • Prefer these types: feat, fix, refactor, perf, docs, test, chore, and ci.
  • Use docs: update changelog for vX.Y.Z for a changelog-only preparation commit.
  • Keep the release script commit as chore: release vX.Y.Z.
  • Keep one logical change per commit. Do not mix formatting-only, dependency, docs, and behavior changes unless the user explicitly asks for a combined release-prep commit.
  • Mark breaking changes with ! after the type or a BREAKING CHANGE: footer, and treat them as a major-version signal.
  • Before committing, check git config --local --get user.name and git config --local --get user.email. If either is missing, ask the user to set repo-local identity with git config --local user.name "Name" and git config --local user.email "[email protected]"; do not write global git config.

Workflow

1. Inspect Release State

Use local repository history:

Run:

git status --short
git describe --tags --abbrev=0
git log "$(git describe --tags --abbrev=0)..HEAD" --oneline --no-decorate

Read the full file on GitHub · 96 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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 · 96 lines · 52 tokens per session scan A f09326908da3

Subscribe to this mod's changes

release is a skill published in the GitHub repository tyql688/sessionview (15 stars, last pushed 14d ago), licensed MIT. It adds 52 tokens to every session and 984 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 workflowPlanningProductivityclaudecodexcursor-cligemini-clikimi-cliopencode
Related

Other skills, from other repositories

exploit-xss

Cross-site scripting (XSS) vulnerability detection and exploitation. Supports reflected XSS, stored XSS, DOM-based XSS, and blind XSS testing. Use this skill when user mentions XSS, cross-site scripting, script injection, or needs to test JavaScript injection in parameters, forms, headers, or DOM sources.

crazyMarky/pentest-skills · 71 tokens

results-storage

SQLite-based persistent storage and reporting system for penetration testing results. Use this skill when user needs to store scan results, query vulnerabilities, generate reports, or manage pentest data across sessions.

crazyMarky/pentest-skills · 40 tokens

exploit-sqli

SQL injection detection and exploitation using sqlmap, manual techniques, and custom payloads. Use this skill when user needs to test for SQL injection vulnerabilities, extract database information, or exploit SQLi in parameters, headers, or cookies.

crazyMarky/pentest-skills · 51 tokens

recon-dir-scan

Directory and file enumeration using ffuf, gobuster, dirsearch, and feroxbuster. Use this skill when user needs to discover hidden directories, enumerate files, find backup files, or map application structure through path fuzzing.

crazyMarky/pentest-skills · 52 tokens

recon-fingerprint

Web fingerprinting and WAF detection using wafw00f, whatweb, nuclei, and httpx. Use this skill when user needs to identify web technologies, detect WAF/CDN, analyze server headers, or fingerprint web applications and frameworks.

crazyMarky/pentest-skills · 55 tokens

recon-subdomain

Subdomain enumeration and DNS reconnaissance using subfinder, amass, dnsx, and other tools. Use this skill when user needs to discover subdomains, perform DNS enumeration, gather DNS records, or find hidden subdomains of a target domain.

crazyMarky/pentest-skills · 54 tokens