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 rstackjs/agent-skills --skill rspress-v2-upgradegit clone --depth 1 https://github.com/rstackjs/agent-skillsWrote 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/rstackjs/agent-skills/rspress-v2-upgrade)<a href="https://agentmods.dev/skills/rstackjs/agent-skills/rspress-v2-upgrade"><img src="https://agentmods.dev/badge/skills/rstackjs/agent-skills/rspress-v2-upgrade/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/rstackjs/agent-skills/rspress-v2-upgrade"><img src="https://agentmods.dev/badge/skills/rstackjs/agent-skills/rspress-v2-upgrade.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 26 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00049 | $0.00553 |
| Opus 5 | $0.00024 | $0.00277 |
| Sonnet 5 | $0.00010 | $0.00111 |
| Haiku 4.5 | $0.00005 | $0.00055 |
Grade A, and why
rspress-v2-upgrade 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 9d 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
Rspress v1 to v2 Upgrade
Workflow
-
Confirm current setup
- Read
package.jsonto identify Rspress and plugin packages in use. - Locate the Rspress config file (commonly
rspress.config.(ts|js|mjs|cjs)). - Check for custom theme files and MDX usage.
- Read
-
Open the official upgrade guide
- Use the v1 → v2 guide as the source of truth:
-
Plan the upgrade path
- List breaking changes that apply to the project's current config, plugins, and theme.
- Note any removed or renamed packages, options, and APIs.
-
Update dependencies
- Replace
rspresswith@rspress/core@^2.0.0. - Remove packages now built into
@rspress/core(e.g.rspress,@rspress/plugin-shiki,@rspress/plugin-auto-nav-sidebar,@rspress/plugin-container-syntax,@rspress/plugin-last-updated,@rspress/plugin-medium-zoom,@rspress/theme-default,@rspress/runtime). - Bump remaining Rspress plugins to latest versions via
npx taze major --include /rspress/ -w -r. - Ensure Node.js >= 20.9.0.
- Replace
-
Apply config and code changes
- Update import paths (
rspress/runtime→@rspress/core/runtime,rspress/theme→@rspress/core/theme,@rspress/theme-default→@rspress/core/theme-original). - If the project has a custom theme (in
themedirectory), use@rspress/core/theme-originalto import the original theme components. - Update the Rspress config to match v2 options and defaults.
- Remove deprecated or unsupported settings.
- Update import paths (
-
Validate
- Run the build and dev server.
- Fix any warnings or errors that appear in the new version. If errors or warnings occur, please refer to the Official Upgrade Guide and first check if it's caused by any omitted or incomplete migration steps.
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.
- 9d ago First seen · 38 lines · 49 tokens per session scan A 6100629888fe
rspress-v2-upgrade is a skill published in the GitHub repository rstackjs/agent-skills (93 stars, last pushed yesterday), licensed MIT. It adds 49 tokens to every session and 553 once invoked, about $0.0002 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
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ralph with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
create-site
Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…
prototype-web
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.
menu-transitions-rtl
Animate react-horizontal-scrolling-menu scrolling and build right-to-left menus: noPolyfill defaults to true since v8, so transitionDuration (default 500), a custom-easing-function transitionBehavior, and per-call ScrollOptions { duration, boundary } on scrollToItem/scrollNext/scrollPrev are silently ignored unless…