Rsdoctor is a build analyzer for Rspack projects that shows how compilation works, what it produces, and where build problems occur. Development teams use it to inspect build artifacts and timing, check build rules, and add custom scans. The catalogue add-ons provide ways to work with Rsdoctor.
Borrowing it
Nothing to install: this file belongs to web-infra-dev/rsdoctor. 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/web-infra-dev/rsdoctor/main/.agents/skills/release-rsdoctor/SKILL.mdgit clone --depth 1 https://github.com/web-infra-dev/rsdoctorWrote 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/web-infra-dev/rsdoctor/release-rsdoctor)<a href="https://agentmods.dev/skills/web-infra-dev/rsdoctor/release-rsdoctor"><img src="https://agentmods.dev/badge/skills/web-infra-dev/rsdoctor/release-rsdoctor/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/web-infra-dev/rsdoctor/release-rsdoctor"><img src="https://agentmods.dev/badge/skills/web-infra-dev/rsdoctor/release-rsdoctor.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.00052 | $0.00439 |
| Opus 5 | $0.00026 | $0.00219 |
| Sonnet 5 | $0.00010 | $0.00088 |
| Haiku 4.5 | $0.00005 | $0.00044 |
Grade A, and why
release-rsdoctor 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.
What it actually says
Release Rsdoctor
Input
- Target version, for example
1.5.8
If the version is missing, ask for it before making changes.
Steps
-
Check the worktree with
git status --short. If there are uncommitted edits, stop and ask the user how to proceed. -
Create and switch to branch
release_v<version>(underscore, not slash). If the branch already exists, stop and ask the user how to proceed. -
Set every publishable package under
packages/to the target version, except@rsdoctor/agent-cli:pnpm --filter './packages/*' \ --filter '!@rsdoctor/agent-cli' \ exec npm pkg set 'version=<version>'These packages always move together as a fixed group, even if only one package changed. Do not update private tooling workspaces outside
packages/. -
Regenerate the lockfile from the updated package manifests:
pnpm install --lockfile-only -
Review the diff. Confirm every package in the fixed group has exactly the target version,
@rsdoctor/agent-cliis unchanged, andpnpm-lock.yamlis updated. -
Commit with this exact message:
release: v<version> -
Push the branch, then create a GitHub PR with
gh pr create. Use the same text for the PR title:release: v<version> -
Read the repository's PR template when available and follow its current headings and guidance. Explain that the PR prepares release
v<version>by updating the fixed group's package versions and lockfile. Include the release link:https://github.com/web-infra-dev/rsdoctor/releases/tag/v<version>.
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 Changed · -3 lines 84bdfc88ebdc
- 10d ago First seen · 46 lines · 52 tokens per session scan A 2eb3564258ba
release-rsdoctor is a skill published in the GitHub repository web-infra-dev/rsdoctor (1,139 stars, last pushed today), licensed MIT. It adds 52 tokens to every session and 439 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
update-changelog
Update the CHANGELOG.md files of C# projects. Parameters: csroot C# SDK repository root.
pump-build-release
Build and release pipeline for the Pump SDK — tsup TypeScript builds, Cargo release profiles, semantic release with commitizen, npm publishing, linting, Makefile targets, Vercel deployment, and MCP server distribution.
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.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
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.
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.