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/Amey-Thakur/AI-SKILLSWrote 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/amey-thakur/ai-skills/release-notes)<a href="https://agentmods.dev/commands/amey-thakur/ai-skills/release-notes"><img src="https://agentmods.dev/badge/commands/amey-thakur/ai-skills/release-notes/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/amey-thakur/ai-skills/release-notes"><img src="https://agentmods.dev/badge/commands/amey-thakur/ai-skills/release-notes.svg" alt="Reviewed on agentmods" width="80" 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.00021 | $0.00331 |
| Opus 5 | $0.00010 | $0.00166 |
| Sonnet 5 | $0.00004 | $0.00066 |
| Haiku 4.5 | $0.00002 | $0.00033 |
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.
What it actually says
You were invoked as a slash command. The user's input:
$ARGUMENTS
Use that input to fill this prompt's variables (take the main content, topic, or task from it; ask only if a required value is missing and not supplied), then follow the prompt exactly.
Write release notes from these changes:
{changes}
Audience: {audience}
Rules:
- Write for the reader, not from the commit log: translate "refactored the auth module" into what it means for them ("sessions now stay active for 24 hours"). If a change does not affect the reader, drop it or minimize it.
- Group by type: New, Improved, Fixed, and (prominently) Breaking changes / action required. Lead with what matters most to this audience.
- Call out breaking changes loudly, with what the reader must do to migrate: this is the most important part, never bury it.
- Concise and scannable: a line per change, benefit-first. Include the version and date.
Output in markdown, ready to publish (keep-a-changelog style). Rules: honest about what shipped, no marketing spin on bug fixes, no vague "various improvements and bug fixes" that tells the reader nothing. If the changes list is raw commits, filter the noise (internal refactors, test-only changes) unless the audience is developers who want it all.
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 · 38 lines · 21 tokens per session scan A 6a72ce93fe75
release-notes is a command published in the GitHub repository Amey-Thakur/AI-SKILLS (7 stars, last pushed 3d ago), licensed MIT. It adds 21 tokens to every session and 331 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-09-06.
Other commands, from other repositories
publish
Publish oh-my-opencode to npm via GitHub Actions workflow.
get-unpublished-changes
Compare HEAD with the latest published npm versions and list all unpublished changes by release layer.
ship
Seen on their staging, then live. Rollback you have run.
ship-and-observe
Take merged, green code to a verified, monitored production release — deploy, confirm the revision is live, smoke-test, observe, and roll back if needed.
release-prep
Review the local working tree, commit, push, open a PR, drive it merge-ready — do not merge.
OPSX: Archive
Archive a completed change in the experimental workflow.