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.
git clone --depth 1 https://github.com/Project-VIC-International/Agentic-AI-Development-CourseWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/rules/project-vic-international/agentic-ai-development-course/release-management)<a href="https://agentmods.dev/rules/project-vic-international/agentic-ai-development-course/release-management"><img src="https://agentmods.dev/badge/rules/project-vic-international/agentic-ai-development-course/release-management.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.02250 | $0.02250 |
| Opus 5 | $0.01125 | $0.01125 |
| Sonnet 5 | $0.00450 | $0.00450 |
| Haiku 4.5 | $0.00225 | $0.00225 |
Grade A, and why
release-management 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 7d 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Management: Changelog and Documentation
Every minor and major release of this tool requires updated CHANGELOG.md and README.md. These files are the public record of what shipped and how to use it. Incomplete release documentation is a release blocker — CI MUST fail a release if the changelog is missing an entry for the version being tagged.
For a CAC mission tool, this is more than good engineering hygiene. It is what lets a peer agency, a NIST CFTT validator, a defense expert, or a future you understand what version of the tool produced a particular piece of evidence. A finding from this tool is only as defensible as the changelog entry for the version that produced it.
CHANGELOG.md Requirements
This project follows Keep a Changelog and Semantic Versioning.
When to Update
- Every version bump — no version ships without a changelog entry.
- Update the changelog as features land on the branch, not in a last-minute batch before release. Each PR that adds, changes, or fixes functionality SHOULD include an entry under the
[Unreleased]section at the top of the file. - Spec-driven features MUST add a changelog entry as part of
/speckit.implement— the spec is not "done" until the user-facing change is documented.
Entry Format
Every version entry MUST include:
- Version number and date in ISO 8601:
## [v1.1.0] - 2026-05-01 - Sections using standard categories:
Added,Changed,Fixed,Removed,Security,Deprecated,Performance - Each item MUST be a concrete, user-facing description — not an internal implementation detail
- Reference the affected module / package in parentheses where helpful:
(ingest),(reporting),(mcp) - Reference related GitHub issues or PRs:
(#42),(#19) - For security-relevant changes, include the control family:
(NIST AC-7, CJIS 5.6.2)per thesecurity-compliancerule - For performance changes, include before / after benchmark numbers and link to the autoresearch run that produced them — per the
auto-researchrule, the spec floor ratchets to the new baseline
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.
- 7d ago First seen · 167 lines · 2,250 tokens per session scan A b506ce06e34f
release-management is a cursor rule published in the GitHub repository Project-VIC-International/Agentic-AI-Development-Course (5 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 2,250 tokens to every session, about $0.0112 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 cursor rules, from other repositories
monorepo-versioning
Internal peerDependency ranges and Changesets conventions for the SDK monorepo — avoid major-version cascades.
release-notes
Generate changelog entries and GitHub releases from git history. Categorizes commits into features, fixes, breaking changes, and docs. Supports conventional commits, PR-based grouping, and semantic versioning. Creates formatted CHANGELOG.md entries and GitHub releases.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
release-checklist
What to update with each code change or version release.
release-policy
Release, versioning, and signing policy for setmac.
bump-project-version
The user can provide version in one of three ways.