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 commands/zts0hg/codexspec/release-notesgit clone --depth 1 https://github.com/Zts0hg/codexspecWhat 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.00033 | $0.02473 |
| Opus 5 | $0.00016 | $0.01236 |
| Sonnet 5 | $0.00007 | $0.00495 |
| Haiku 4.5 | $0.00003 | $0.00247 |
Grade A, and why
release-notes 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.
How it starts
The opening of the file, as written. The whole thing — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Constitution Compliance (MANDATORY)
Before generating release notes:
- Check for Constitution File: Look for
.codexspec/memory/constitution.md - If Constitution Exists:
- Load and read relevant principles (especially documentation and versioning standards)
- Ensure the generated notes align with constitutional guidelines
- If No Constitution Exists: Proceed with the defaults below
Language Preference
IMPORTANT: Before generating output, read the project's language configuration from .codexspec/config.yml.
Generated-content language priority:
- If
language.commitis set, use that language for the CHANGELOG entry and release body - Otherwise, use
language.outputas fallback - If neither is configured, default to English
Note:
- Section headings that are format keywords (
Added,Changed,Fixed, etc.) and technical terms (API, JWT, OAuth) may remain in English when appropriate. - The
## [Unreleased]/## [X.Y.Z]version markers and ISO dates are format, not prose — keep them as-is.
User Input
$ARGUMENTS
Role
You generate release notes from git history for this project, whatever its release process.
You make no assumption about how the project releases: there may be no publish.sh, no CI, no
particular hosting platform, and no particular versioning scheme (semver, CalVer, and date tags are
all possible). Every behavior below degrades gracefully when such an assumption does not hold.
You produce two layered outputs from the same analysis:
- A developer CHANGELOG.md entry in Keep a Changelog format.
- A user-facing release body derived from it.
You own no versioning and mutate no git state (see Forbidden Operations).
Forbidden Operations (CRITICAL)
This command is a generator, sharing the safety discipline of commit-staged and pr.
UNDER NO CIRCUMSTANCES:
git add/git commit/git reset/git checkout/git restore/git stash/git rm— the command MUST NEVER modify the git staging area and MUST NEVER create a commit.- Overwrite
CHANGELOG.mdwholesale withWrite, or rewrite / reorder / delete any existing CHANGELOG entry. - Decide or "own" a version bump; tag; publish; or create a GitHub/GitLab release.
- Include any AI attribution in generated content — no
Co-Authored-By, "Generated with", robot emoji, or references to AI tools/agents.
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.
- 2d ago First seen · 213 lines · 33 tokens per session scan A fff4dfc81157
release-notes is a command published in the GitHub repository Zts0hg/codexspec (5 stars, last pushed 3d ago), licensed MIT. It adds 33 tokens to every session and 2,473 once invoked, about $0.0002 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-31.
Other commands, from other repositories
create-bucket-docs
Create documentation for a Lingo.dev bucket type using analysis output.
finmind
You are a FinMind financial data assistant. Help the user query financial data from the FinMind API based on their natural language request.
en
Switch Claude Code back to English (short alias for /english).
zh
切换 Claude Code 为简体中文（/chinese 的短别名）.
review-agentready
AgentReady-specific code review with attribute mapping and score impact analysis.
docs
Make sure that @README.md and @CLAUDE.md are up to date with current code structure, specification, architecture, features, environment variables. Make sure to also update the translated version at @READMEru.md. Also if there are new tools added to the project - make sure they are documented in @README.md…