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 redhat-developer/rhdh-skills --skill rhdh-backstage-upgradegit clone --depth 1 https://github.com/redhat-developer/rhdh-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/redhat-developer/rhdh-skills/rhdh-backstage-upgrade)<a href="https://agentmods.dev/skills/redhat-developer/rhdh-skills/rhdh-backstage-upgrade"><img src="https://agentmods.dev/badge/skills/redhat-developer/rhdh-skills/rhdh-backstage-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/redhat-developer/rhdh-skills/rhdh-backstage-upgrade"><img src="https://agentmods.dev/badge/skills/redhat-developer/rhdh-skills/rhdh-backstage-upgrade.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.00166 | $0.01040 |
| Opus 5 | $0.00083 | $0.00520 |
| Sonnet 5 | $0.00033 | $0.00208 |
| Haiku 4.5 | $0.00017 | $0.00104 |
Grade A, and why
rhdh-backstage-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 6d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RHDH Backstage Upgrade
Own version numbers. Which @backstage/* release a checkout sits on, which
release it should move to, and everything that breaks in between.
Start here
- Read
package.jsonandbackstage.jsonbefore changing any dependency. - Establish the target RHDH version. Prefer an explicit user or repository
value; otherwise invoke
/rhdh-contextfor the checked-in compatibility matrix. If it is unavailable, ask the user for the target RHDH and Backstage versions rather than guessing. - Report current versions and the proposed target before running a bump.
Route by outcome
| Outcome | Load and follow |
|---|---|
| Run the whole upgrade | workflows/upgrade-backstage.md |
| Find the current versions and any misalignment | references/discover-versions.md |
| Choose the target release | references/determine-target.md |
| Bump the dependency set | references/bump-deps.md |
| Move imports off renamed or relocated packages | references/migrate-packages.md |
| Work through the breaking changes between releases | references/fix-breaking-changes.md |
| Verify the upgrade | references/verify-upgrade.md |
Boundaries
- This skill owns version numbers. It does not change what a plugin's extensions are or how they attach.
/rhdh-plugin-nfs-migrationowns extension shape: converting a legacy frontend plugin's extensions into New Frontend System Blueprints. The two skills meet whenever an upgrade is a prerequisite for a migration, or a migration surfaces an outdated dependency set. Bump the versions here; change the extensions there./backstage-api-changesowns the NFS API deltas between the early alpha and the current GA surface. Invoke it by name when an upgrade breaks NFS code — a removedNavItemBlueprint, aconfig.schemablock that must becomeconfigSchema, or a renamed blueprint param./rhdh-contextowns the RHDH-to-Backstage compatibility matrix./rhdh-plugin-authoringowns non-mechanical source changes the upgrade exposes./rhdh-pr-createowns staging, commits, and pull requests.
What ships with it
8 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.
- 6d ago Changed · +6 lines · +16 tokens per session 1865e4c788e6
- 10d ago First seen · 83 lines · 150 tokens per session scan A 604c38ea406c
rhdh-backstage-upgrade is a skill published in the GitHub repository redhat-developer/rhdh-skills (16 stars, last pushed yesterday), licensed Apache-2.0. It adds 166 tokens to every session and 1,040 once invoked, about $0.0008 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…