repo-standards-router

repo-standards-router is a skill for Claude Code from chf3198/copilot-governance. It costs 29 tokens per session (1,257 once invoked), scanned A, original, MIT.

A decision guide that identifies what kind of application a repository contains and selects the matching development rules, policy profile, and checks. A repository is the project folder and its version-controlled files.

In plain words
What is it for?
Use it when choosing standards for a repository, handling projects with more than one application type, defining verification checks, or deciding when GitHub workflow governance needs a separate review.
Why use it?
It prevents applying irrelevant standards or rewriting broad policies when the project type or required evidence is still unclear.

Skill for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter. Also seen: reads .claude/ paths; mentions Codex.

Good fit Use it when choosing standards for a repository, handling projects with more than one application type, defining verification checks, or deciding when GitHub workflow governance needs a separate review.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/chf3198/copilot-governance/repo-standards-router
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 chf3198/copilot-governance --skill repo-standards-router
Clone the repo
git clone --depth 1 https://github.com/chf3198/copilot-governance

Made for: Claude Code.

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.

agentmods badge for repo-standards-router

README.md
[![agentmods](https://agentmods.dev/badge/skills/chf3198/copilot-governance/repo-standards-router/github.svg)](https://agentmods.dev/skills/chf3198/copilot-governance/repo-standards-router)
Your own site
<a href="https://agentmods.dev/skills/chf3198/copilot-governance/repo-standards-router"><img src="https://agentmods.dev/badge/skills/chf3198/copilot-governance/repo-standards-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.

agentmods 80×15 button for repo-standards-router

Your own site · 80×15
<a href="https://agentmods.dev/skills/chf3198/copilot-governance/repo-standards-router"><img src="https://agentmods.dev/badge/skills/chf3198/copilot-governance/repo-standards-router.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 29 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,257 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00029 $0.01257
Opus 5 $0.00015 $0.00629
Sonnet 5 $0.00006 $0.00251
Haiku 4.5 $0.00003 $0.00126

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

Security

Grade A, and why

repo-standards-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 10d 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.

skills/repo-standards-router/SKILL.md · 137 lines

How it starts

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

Repo Standards Router

Purpose

Select the smallest correct standards stack for a repo, based on primary app type, overlapping overlays, and risk profile.

Scope boundary

This skill is the router for repository standards composition (app-type + overlays), not the router for GitHub workflow governance.

  • Owns: standards branch selection, verification gates, branch-promotion candidates.
  • Does not own: ticket lifecycle execution, review/merge administration, ruleset architecture, merge queue readiness, Actions hardening.

If the request includes GitHub workflow governance controls, hand off to github-ops-tree-router after standards selection.

Hard constraints

  1. No broad policy rewrites in one pass.
  2. Maximum 8 recommendations.
  3. Must return explicit verification gates.
  4. If repository type is unclear, return NO_CHANGE + missing evidence.
  5. Prefer existing classes + overlays over creating a new branch.
  6. For app-types with first-class versioned distribution channels, include a version-selectability control in release recommendations.

Decision flow

  1. Detect primary_type from runtime intent and repository artifacts.
  2. Detect secondary_types only when overlap is clear and evidence-backed.
  3. Apply core-baseline controls.
  4. Apply primary-type controls per the app-type classification (the core-baseline controls above plus the per-type overlays selected in steps 5-6).
  5. Apply selected overlays (security, collaboration, release, optional observability).
  6. Calibrate severity with policy_profile.
  7. Emit actionable controls and checks.

Handoff protocol

Set handoff_required=yes when any requested control includes:

  • branch protection or rulesets,
  • merge queue policy,
  • Actions token/pinning/OIDC/runner hardening,
  • ticket/PR lifecycle administration.

Then set handoff_skill=github-ops-tree-router and include a short reason.

Output format (required)

STANDARDS_ROUTER_REPORT
primary_type: <website-static|web-app|library-sdk|infra-automation>
secondary_types: <none|comma-separated types>
overlays: <none|security,collaboration,release,observability>
policy_profile: <strict|standard|light>
confidence: <high|medium|low>

selected_branches:
- core-baseline
- <primary-type-branch>
- <overlay-branches>

handoff:
- required: <yes|no>
- handoff_skill: <none|github-ops-tree-router>
- reason: <none|why governance routing is needed>

controls:
1) priority: <P1|P2|P3>
   area: <security|testing|docs|release|quality|accessibility|seo|supply-chain>
   change: <specific control>
   verification: <objective check>

missing_controls:
- <none or control gaps not yet covered by current branches>

skills_to_run_next:
- <none|web-regression-governance|repo-profile-governance|github-ops-tree-router|workflow-self-anneal>

decision:
- <apply|defer|NO_CHANGE>

missing_evidence:
- <none or required artifacts>

evolution_todos:
- <only if repeated gaps suggest future branch creation>

Read the full file on GitHub · 137 lines

Files

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.

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.

  1. 10d ago First seen · 137 lines · 29 tokens per session scan A c288390eadf7

Subscribe to this mod's changes

repo-standards-router is a skill published in the GitHub repository chf3198/copilot-governance (2 stars, last pushed 1mo ago), licensed MIT. It adds 29 tokens to every session and 1,257 once invoked, about $0.0001 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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…

vercel/next.js · 83 tokens

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…

vercel/next.js · 170 tokens

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…

vercel/next.js · 103 tokens