React Router is a routing system for React applications that maps URLs to the interface shown on screen. Developers use it either as a small library within their own application structure or as part of a full React framework.
Borrowing it
Nothing to install: this file belongs to remix-run/react-router. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/remix-run/react-router/main/.agents/skills/prepare-release-notes/SKILL.mdgit clone --depth 1 https://github.com/remix-run/react-routerWrote 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/remix-run/react-router/prepare-release-notes)<a href="https://agentmods.dev/skills/remix-run/react-router/prepare-release-notes"><img src="https://agentmods.dev/badge/skills/remix-run/react-router/prepare-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/skills/remix-run/react-router/prepare-release-notes"><img src="https://agentmods.dev/badge/skills/remix-run/react-router/prepare-release-notes.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Snyk pass
- 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.00086 | $0.00959 |
| Opus 5.5 | $0.00034 | $0.00384 |
| Sonnet 5.5 | $0.00017 | $0.00192 |
| Haiku 4.5 | $0.00009 | $0.00096 |
Grade A, and why
prepare-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.
How it starts
The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prepare Release Notes
Polish pending React Router change files and add manual release notes only when the release needs narrative context beyond the generated change lists.
Workflow
- Inspect local state:
git status --short
find packages -path '*/.changes/*.md' -not -name README.md -not -name .gitkeep -print | sort
-
Read every pending change file. Do not edit generated changelogs or released notes directly.
-
Normalize each change file:
- Remove
feat:,feat(...),fix:, andfix(...)semantic-commit prefixes from prose - Use present or imperative tense for the first line and top-level release bullets: prefer
Add,Fix,Remove,Support,Stabilize,Preserve,Update,Avoid,Prevent,Throw,Warn,Expose - Nested detail bullets can stay explanatory when they expand on the parent bullet; do not rewrite them solely to force present or imperative tense
- Remove terminal sentence periods from bullet items because release generation appends PR/commit links after the first bullet line
- Remove terminal sentence periods from nested bullet items too, unless the punctuation is part of code, a URL, an abbreviation, a version number, or another token where removing it would be wrong
- If one bullet contains multiple sentences, split it into a shorter parent bullet plus nested bullet items
- Keep the first line concise and user-facing; use nested bullets for details or migration notes
- Remove
-
Review whether
scripts/changes/whats-changed.mdis needed:- Read
CHANGELOG.mdexamples orreferences/whats-changed.mdwhen uncertain - Add
scripts/changes/whats-changed.mdonly for features, future flag stabilizations, unstable flags, migration guidance, breaking bug fixes, or complex behavior that needs long-form text or examples - Do not add it for ordinary bug fixes, dependency cleanup, internal refactors, or release bullets that are already clear
- If adding it, write the body only; the release script adds
### What's Changedwhen missing
- Read
What ships with it
2 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 · 99 lines · 86 tokens per session scan A c2476870304a
prepare-release-notes is a skill published in the GitHub repository remix-run/react-router (56,622 stars, last pushed today), licensed MIT. It adds 86 tokens to every session and 959 once invoked, about $0.0003 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
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
release
Fully automate a release with version-bump and childhood.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.