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/thapaliyabikendra/ai-artifacts/release-notesgit clone --depth 1 https://github.com/thapaliyabikendra/ai-artifactsWrote 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/commands/thapaliyabikendra/ai-artifacts/release-notes)<a href="https://agentmods.dev/commands/thapaliyabikendra/ai-artifacts/release-notes"><img src="https://agentmods.dev/badge/commands/thapaliyabikendra/ai-artifacts/release-notes.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 | $0.00016 | $0.01133 |
| Opus 5 | $0.00008 | $0.00566 |
| Sonnet 5 | $0.00003 | $0.00227 |
| Haiku 4.5 | $0.00002 | $0.00113 |
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 4d 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 — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate Release Notes
Version: $ARGUMENTS.version From: $ARGUMENTS.from Format: $ARGUMENTS.format
Instructions
Step 1: Gather Changes
Run git commands to collect commits:
# Find last release tag
git describe --tags --abbrev=0
# Get commits since last release
git log [from]..HEAD --oneline --no-merges
# Get merged PRs
git log [from]..HEAD --merges --oneline
Step 2: Categorize Changes
Parse commit messages and categorize:
| Prefix | Category | Emoji |
|---|---|---|
| feat: | Features | ✨ |
| fix: | Bug Fixes | 🐛 |
| perf: | Performance | ⚡ |
| docs: | Documentation | 📚 |
| refactor: | Refactoring | ♻️ |
| test: | Tests | ✅ |
| chore: | Maintenance | 🔧 |
| security: | Security | 🔒 |
| breaking: | Breaking Changes | 💥 |
Step 3: Generate Release Notes
Markdown Format
# Release Notes - v[VERSION]
**Release Date**: [YYYY-MM-DD]
**Previous Version**: [previous version]
## Highlights
[2-3 sentence summary of the most important changes in this release]
## ✨ New Features
- **[Feature Name]**: [Brief description] ([#PR](link))
- [Additional detail if needed]
- **[Feature Name]**: [Brief description] ([#PR](link))
## 🐛 Bug Fixes
- Fixed [issue description] ([#PR](link))
- Fixed [issue description] ([#PR](link))
## ⚡ Performance Improvements
- [Improvement description] ([#PR](link))
## 💥 Breaking Changes
> ⚠️ **Action Required**: These changes may require updates to your code.
- **[Change]**: [Description and migration path]
```diff
- old code
+ new code
🔒 Security Updates
- [Security fix description]
♻️ Refactoring
- [Refactoring description]
📚 Documentation
- [Documentation update]
🔧 Maintenance
- [Maintenance item]
Upgrade Guide
From v[previous] to v[current]
- Step 1: [Action]
- Step 2: [Action]
- Run migrations:
dotnet ef database update
Breaking Change Details
[Breaking Change 1]
Before:
// Old usage
After:
// New usage
Contributors
Thanks to everyone who contributed to this release:
- @[contributor1]
- @[contributor2]
Full Changelog
Compare link: v[previous]...v[current]
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.
- 4d ago First seen · 233 lines · 16 tokens per session scan A baf69b3103d5
release-notes is a command published in the GitHub repository thapaliyabikendra/ai-artifacts (24 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 16 tokens to every session and 1,133 once invoked, about $0.0001 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.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.