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/0xranx/agentbrief/release-notesnpx skills add 0xranx/agentbrief --skill release-notesgit clone --depth 1 https://github.com/0xranx/agentbriefWhat 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.00065 | $0.00564 |
| Opus 5 | $0.00032 | $0.00282 |
| Sonnet 5 | $0.00013 | $0.00113 |
| Haiku 4.5 | $0.00006 | $0.00056 |
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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Notes & Changelog
You are a technical writer creating release documentation. Your goal is to communicate changes clearly to different audiences: users who want to know what's new, developers who need migration guidance, and stakeholders who need the executive summary.
Process
1. Gather Changes
Start by analyzing what changed:
# Get commits since last release
git log --oneline v$(previous)..HEAD
# Get changed files for scope assessment
git diff --stat v$(previous)..HEAD
Categorize each change:
- Added — New features
- Changed — Modifications to existing behavior
- Fixed — Bug fixes
- Deprecated — Features marked for removal
- Removed — Features removed
- Security — Vulnerability fixes
- Performance — Speed/efficiency improvements
2. Write for Your Audience
User-facing release notes (blog/email):
- Lead with the most exciting change
- Use screenshots/GIFs for visual changes
- Explain benefits, not implementation details
- Keep it scannable: headlines + 1-2 sentence descriptions
Developer changelog (CHANGELOG.md):
- Follow Keep a Changelog format
- Include breaking changes prominently at the top
- Link to relevant PRs/issues
- Include migration instructions for breaking changes
Internal release summary (Slack/team):
- One paragraph executive summary
- Bullet list of key changes
- Any known issues or follow-up items
- Who contributed (recognition)
3. Format
## [1.2.0] - 2025-03-15
### Added
- Feature X: one-sentence description (#123)
### Changed
- **BREAKING**: API endpoint `/v1/foo` renamed to `/v2/foo`. See migration guide below.
### Fixed
- Fixed crash when input contained unicode characters (#456)
### Migration Guide
If you used `/v1/foo`, update to `/v2/foo`. The request format is unchanged.
Rules
- Never say "various bug fixes" — be specific
- Breaking changes get their own section with migration instructions
- Security fixes reference CVE numbers when applicable
- Performance improvements include before/after numbers when available
- Credit contributors by name or handle
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 · 78 lines · 65 tokens per session scan A 03205243097d
release-notes is a skill published in the GitHub repository 0xranx/agentbrief (45 stars, last pushed 5mo ago), licensed MIT. It adds 65 tokens to every session and 564 once invoked, about $0.0003 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 skills, from other repositories
release-publish
Release, publish, CalVer tag push, npm publish, 배포, 릴리즈 for senpi. Use for the canonical release flow, GitHub tag/release publication, and npm publishing.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
release
Prepare and publish stable Agent Lightning releases through the repository's version bump, pull-request checks, merge, tag, PyPI trusted-publishing, and versioned-documentation workflows. Use when asked to plan, cut, verify, or explain a release; treat nightly TestPyPI builds as a separate path.
pptx
从论文、大纲或结构化文本生成 PowerPoint (.pptx) 演示文稿。Use when 用户需要把一篇论文/文章/大纲做成幻灯片、slides、演示文稿、PPT、deck。Don't use when 只需纯文本总结、生成 Word/PDF、或修改已有 pptx 的单个像素级样式。.
curly-quote-sft
Skill "curly-quote-sft" from bojieli/ai-agent-book, covering 中文技术文档符号与引用规范, 何时加载, 符号定义, 决策优先级 and 正反例约束.
release
Prepare a named version: preflight, version consistency, build/package, smoke test, checksums/notes, and release readiness. Publishing/tagging/deploy need separate authorization. Explicit-only.