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/release-react-router/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/release-react-router)<a href="https://agentmods.dev/skills/remix-run/react-router/release-react-router"><img src="https://agentmods.dev/badge/skills/remix-run/react-router/release-react-router/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/release-react-router"><img src="https://agentmods.dev/badge/skills/remix-run/react-router/release-react-router.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.00053 | $0.01253 |
| Opus 5.5 | $0.00021 | $0.00501 |
| Sonnet 5.5 | $0.00011 | $0.00251 |
| Haiku 4.5 | $0.00005 | $0.00125 |
Grade A, and why
release-react-router 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 today.
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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release React Router
Use the existing release automation. Read DEVELOPMENT.md, .github/workflows/release.yml, and scripts/changes/{pr,publish}.ts for the current process and tag rules. This skill covers generated release PRs; experimental releases use a separate workflow.
A request to perform a release authorizes merging the verified PR and following publication. A readiness-only request stops with the review. Creating or editing this skill does not authorize a live release.
Review the release PR
- Find the generated release PR in
remix-run/react-router, targetingmainby default or the requestedv7/existinghotfixbranch. Confirm its source repository and generated branch matchscripts/changes/pr.ts. Attach the PR to the chat when the app provides that tool. - Record the exact head SHA and current base tip. Require the candidate to contain that tip; otherwise wait for automatic PR regeneration and review the updated head. Use GitHub APIs or fetched Git objects to inspect files without changing the user's checkout.
- Review the diff for the expected package version bumps, root/package changelogs, deleted pending change files, and consumption of
scripts/changes/whats-changed.mdwhen present. Confirm the notes represent the pending changes and preserve any manual narrative. Under the current generator, package manifests change only their version; investigate extra paths or fields. - Capture the expected package/version pairs and their npm/git tags from the candidate and current publish script. Discover the package set and versions each run. For non-main releases, record GitHub's current latest release ID before merging so it can be checked afterward.
- Use PR CI for build, test, typecheck, lint, and integration validation. Check all required and applicable jobs on the reviewed head/test merge, accounting for current workflow path filters and intentional matrix skips. Pending, failed, canceled, missing, or stale checks hold the release. No local dependency install, build, packing, consumer smoke, or regeneration is part of the normal release review.
What ships with it
1 file 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.
- today First seen · 52 lines · 53 tokens per session scan A 3baf8b70ba7d
release-react-router is a skill published in the GitHub repository remix-run/react-router (56,622 stars, last pushed today), licensed MIT. It adds 53 tokens to every session and 1,253 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-10-24.
Other skills, from other repositories
git-workflow
Guided git workflows: prepare PRs, clean up branches, resolve merge conflicts, handle monorepo tags, squash-and-merge patterns. Use when asked to prepare a PR, clean branches, resolve conflicts, or tag a release.
github-release
Prepare and publish GitHub releases. Sanitizes code for public release (secrets scan, personal artifacts, LICENSE/README validation), creates version tags, and publishes via gh CLI. Trigger with 'release', 'publish', 'open source', 'prepare for release', 'create release', or 'github release'.
publish-notes
Draft user-facing release notes, store changelogs, and internal publish summaries.
releasing-weaverse-sdks
Use when releasing @weaverse/ npm packages, bumping SDK versions, publishing to npm, or shipping the Weaverse SDKs. Triggers on "release sdk", "release weaverse", "publish packages", "release core", "release schema", "bump sdk version", "ship sdks".
deployment-rules
Release/deployment standards — semantic-release, commitlint, version sync, the updater. Load for /prepare-release and changes to release.config.mjs / commitlint / workflows / version files. Owned by project-steward.
deployment-procedures
Production deployment principles and decision-making. Safe deployment workflows, rollback strategies, and verification. Teaches thinking, not scripts.