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 skills add jnMetaCode/ai-coding-guide --skill templatesgit clone --depth 1 https://github.com/jnMetaCode/ai-coding-guideWrote 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/skills/jnmetacode/ai-coding-guide/templates)<a href="https://agentmods.dev/skills/jnmetacode/ai-coding-guide/templates"><img src="https://agentmods.dev/badge/skills/jnmetacode/ai-coding-guide/templates/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/skills/jnmetacode/ai-coding-guide/templates"><img src="https://agentmods.dev/badge/skills/jnmetacode/ai-coding-guide/templates.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00059 | $0.00610 |
| Opus 5.5 | $0.00024 | $0.00244 |
| Sonnet 5.5 | $0.00012 | $0.00122 |
| Haiku 4.5 | $0.00006 | $0.00061 |
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 1mo 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
Release Notes Drafter
Generate clear, user-facing release notes from git log between two refs.
When to fire
- User mentions: "release notes", "changelog", "what shipped", "summarize this milestone"
- A git ref range or version tag is in scope (e.g.
v1.2.0..HEAD,last-tag..main)
Inputs you should gather
- The two refs (default:
<latest tag>..HEADif user didn't specify) - Audience: end users (default), API consumers, internal team
- Output format: markdown (default), JSON, or plain text
Steps
- Run
git log <from>..<to> --pretty=format:'%h%x09%s%x09%an' --no-merges - For each commit, classify:
feat:/add:→ Featuresfix:/bugfix:→ FixesBREAKING CHANGE:(in body) → Breaking (top of doc, explicit migration note)- everything else (
chore:,docs:,refactor:,test:) → omit unless user-visible
- For each entry, rewrite the commit message in user-facing language (no
feat(api):prefix; no internal jargon) - If there's a PR number in the commit (
(#1234)), link it - Group by category, sort by impact (breaking > features > fixes > minor)
Output template
## <version> — <date>
### ⚠️ Breaking changes
- <one-sentence summary>. **Migration:** <what to do>. ([#PR])
### ✨ Features
- <user-visible benefit>. ([#PR])
### 🐛 Fixes
- <symptom that's now fixed>. ([#PR])
Gotchas
- Don't dump raw commit messages — rewrite from the user's perspective
- Squash-merged repos: each merge commit covers many internal commits; read the PR description for context
- Conventional Commit
chore:anddocs:rarely belong in user-facing notes - If
BREAKING CHANGE:is in the body of afeat:, the entry must surface as Breaking, not Feature - For monorepos, prefix entries with the affected package name (
[@org/auth])
References
- See
references/conventional-commits.mdfor the full type list - See
examples/v1.2.0.mdfor a polished sample
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 60 lines · 59 tokens per session scan A 6c21c88af17f
release-notes is a skill published in the GitHub repository jnMetaCode/ai-coding-guide (544 stars, last pushed yesterday), licensed Apache-2.0. It adds 59 tokens to every session and 610 once invoked, about $0.0002 per session on Opus 5.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
finishing-a-development-branch
A process for finishing a completed development branch. A branch is a separate line of code changes that can later be merged or submitted as a pull request.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.
release-notes-generator
Generate release notes in 3 formats (CHANGELOG.md, PR body, Slack announcement) from git commits. Automatically categorizes changes and converts technical language to user-friendly messaging. Use for releases, changelogs, version notes, what's new summaries, or ship announcements.
release-notes
Generate release notes in multiple formats from git commits.
ship
Comprehensive pre-deployment verification to ensure release readiness.
talk-stage2-research
Performs git archaeology, changelog analysis, and builds a verified factual timeline by cross-referencing git history with source material. REX mode only (skipped automatically in Concept mode). Use when building a REX talk and you need verified commit metrics, release timelines, and contributor data from a git…