What is backstage-repo-discovery?

A read-only guide for mapping an unfamiliar Backstage monorepo, which is one repository containing multiple related packages. It identifies the app structure, plugins, configuration layers, Node and package-manager setup, and real validation commands.

Use it at the start of Backstage work to identify packages, frontend and backend composition, configuration sources, supported tooling, and the checks the repository expects.

It gives developers a reliable picture of the repository before they change code or choose commands.

backstage-repo-discovery — Skill for Claude Code by bendaamerahmed

Install

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.

Any agent

npx skills add bendaamerahmed/backstage-idp-plugin --skill backstage-repo-discovery

Clone the repo

git clone --depth 1 https://github.com/bendaamerahmed/backstage-idp-plugin

Made for: Claude Code.

Or install backstage-idp, the plugin that ships this one along with the rest of its 15 skills, 1 agent.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/bendaamerahmed/backstage-idp-plugin/backstage-repo-discovery/github.svg)](https://agentmods.dev/skills/bendaamerahmed/backstage-idp-plugin/backstage-repo-discovery)

Your own site

<a href="https://agentmods.dev/skills/bendaamerahmed/backstage-idp-plugin/backstage-repo-discovery"><img src="https://agentmods.dev/badge/skills/bendaamerahmed/backstage-idp-plugin/backstage-repo-discovery/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/bendaamerahmed/backstage-idp-plugin/backstage-repo-discovery"><img src="https://agentmods.dev/badge/skills/bendaamerahmed/backstage-idp-plugin/backstage-repo-discovery.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,892 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00037	$0.02892
Opus 5	$0.00018	$0.01446
Sonnet 5	$0.00007	$0.00578
Haiku 4.5	$0.00004	$0.00289

Measured 12d ago against content hash cffae8839b92, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

backstage-repo-discovery 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 12d 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.

plugins/backstage-idp/skills/backstage-repo-discovery/SKILL.md · 174 lines

How it starts

The opening of the file, as written. The whole thing — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Backstage repo discovery

Produce a compact, evidence-backed map of a Backstage monorepo. Every other Backstage skill assumes this map exists. Detect by import source and composition, never by version number alone.

Preconditions

Repository root is readable and ripgrep (rg) is available; fall back to grep -rn.
Discovery is read-only: no installs, builds, or codegen.
If backstage.json, packages/app and packages/backend are all absent, this is probably a standalone plugin repo, not an app monorepo; note that and adapt.

Procedure

Anchor the repo. Read backstage.json at the root — its version field is the release line the app was last bumped to (not the version of any single package). Read root package.json: name, workspaces globs, engines.node, packageManager, resolutions, and the whole scripts block. Record all of it.
Package manager and Node. yarn.lock + .yarnrc.yml means Yarn Berry (Backstage's default; recent scaffolds pin Yarn 4.x via packageManager + corepack). package-lock.json or pnpm-lock.yaml means the repo diverged from upstream — every later command must be translated. Current Backstage supports Node 22 and 24 only; an engines.node allowing older majors means the repo is behind.
Inventory packages. Expand every workspaces glob (commonly packages/* and plugins/*). For each, capture name, version, private, and backstage.role from its package.json. backstage.role (frontend-plugin, backend-plugin, backend-plugin-module, node-library, web-library, common-library, frontend, backend) is the authoritative statement of what a package is — trust it over naming.
Detect the frontend generation. Run all of these and reason from the hits, not from the release line:
- NFS: rg -n "@backstage/frontend-defaults|@backstage/frontend-plugin-api|@backstage/frontend-test-utils" packages plugins
- NFS composition: rg -n "createFrontendPlugin|createFrontendModule|PageBlueprint|ApiBlueprint|EntityCardBlueprint|EntityContentBlueprint" packages plugins
- A NavItemBlueprint hit dates the app: it was removed in v1.51.
- Legacy: rg -n "@backstage/app-defaults|createRoutableExtension|createComponentExtension|<FlatRoutes|bindRoutes" packages plugins
- /alpha consumption: rg -n "from '@backstage/plugin-[^']*/alpha'" packages/app/src
- Hybrid bridge: rg -n "@backstage/core-compat-api|convertLegacyApp" packages/app/src

Read the full file on GitHub · 174 lines

Changes

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.

12d ago First seen · 174 lines · 37 tokens per session scan A cffae8839b92

Subscribe to this mod's changes

backstage-repo-discovery is a skill published in the GitHub repository bendaamerahmed/backstage-idp-plugin (1 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 2,892 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-31.

Claude Code backstage claude claude-code-plugin claude-skills platform-engineering

meta-tags-optimizer

Optimize title tags, meta descriptions, Open Graph, and Twitter cards for maximum click-through rate. Generates multiple A/B test variations with character counting and SERP preview. Use when asked to "optimize title tag", "write meta description", "improve CTR", "Open Graph tags", "fix my meta tags", "social media…

nowork-studio/notfair-plugin · 91 tokens

google-ads-audit

Google Ads account audit and business context setup. Use for account-health audits and business-context setup. Trigger on "audit my ads", "ads audit", "set up my ads", "onboard", "account overview", "how's my account", "ads health check", "what should I fix in my ads", or when the user is new to NotFair and hasn't run…

nowork-studio/notfair-plugin · 86 tokens

sxo

Search Experience Optimization (SXO) — the bridge between SEO and UX/CRO. Audits the full journey from the SERP click to the on-page goal: SERP click-through factors (title/meta/rich results that win the click), then post-click experience signals that keep users and drive conversions — above-the-fold relevance and…

nowork-studio/notfair-plugin · 235 tokens

critical-code-reviewer

Rigorously review code or pull requests for correctness, security, accessibility, maintainability, tests, and edge cases. Use when users request a critical code review, want a guided walkthrough of findings, need implementer-facing feedback, or want to prepare, create, or submit a GitHub pull request review.

posit-dev/skills · 67 tokens

shiny-bslib

Build modern Shiny dashboards and applications using bslib (Bootstrap 5). Use when creating new Shiny apps, modernizing legacy apps (fluidPage, fluidRow/column, tabsetPanel, wellPanel, shinythemes), or working with bslib page layouts, grid systems, cards, value boxes, navigation, sidebars, filling layouts, theming…

posit-dev/skills · 107 tokens

elixir-idioms

OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.

oliver-kriska/claude-elixir-phoenix · 44 tokens