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 skills/zts0hg/codexspec/codexspec-release-notesnpx skills add Zts0hg/codexspec --skill 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.00041 | $0.02444 |
| Opus 5 | $0.00020 | $0.01222 |
| Sonnet 5 | $0.00008 | $0.00489 |
| Haiku 4.5 | $0.00004 | $0.00244 |
Grade A, and why
codexspec: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
the text after the $codexspec:release-notes skill mention
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 · 41 tokens per session scan A 801bca882f55
codexspec:release-notes is a skill published in the GitHub repository Zts0hg/codexspec (5 stars, last pushed 4d ago), licensed MIT. It adds 41 tokens to every session and 2,444 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 skills, from other repositories
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup.
release-check
Pre-release verification checklist. Validates features, tests, docs, security, and quality gates before shipping. Delegates to the Centinela (QA) agent.
comet-release
根据真实版本和分支范围准备 Comet 发布或发布说明更新，保持 Changelog 面向用户、双语网站文档一致、生成资产已验证，并明确 Git 交付边界。Beta、hotfix、版本检查、发布说明或发布就绪检查时使用。.
comet-safe-delivery
在保护无关脏改动、关联 worktree、子模块和用户明确边界的前提下，提交、推送、合并或完成范围明确的 Comet 变更。用户要求提交、推送、合并回目标分支、清理 worktree 或交付已准备好的改动时使用。.
changelog-generator
Generate changelogs from git commits. Use when user says "generate changelog", "update changelog", "what changed since last release", or before preparing a new release.
release-patterns
PR creation, CI/CD validation, merge coordination, and release patterns. Use when creating pull requests, running pre-PR validation, checking CI status, coordinating merges, or managing releases. Do NOT use for routine development commits -- see safe-workflow skill instead.