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 agentmods add skills/chf3198/copilot-governance/github-ops-tree-routernpx skills add chf3198/copilot-governance --skill github-ops-tree-routergit clone --depth 1 https://github.com/chf3198/copilot-governanceWrote 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/chf3198/copilot-governance/github-ops-tree-router)<a href="https://agentmods.dev/skills/chf3198/copilot-governance/github-ops-tree-router"><img src="https://agentmods.dev/badge/skills/chf3198/copilot-governance/github-ops-tree-router.svg" alt="Measured on agentmods" 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 | $0.00027 | $0.00715 |
| Opus 5 | $0.00014 | $0.00358 |
| Sonnet 5 | $0.00005 | $0.00143 |
| Haiku 4.5 | $0.00003 | $0.00072 |
Grade A, and why
github-ops-tree-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 3d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Ops Tree Router
Purpose
Select the correct specialized GitHub operations path with minimal overlap and valid feature support.
Capability-first protocol
For goals involving rulesets, merge queue, Actions security, or plan-sensitive controls,
run github-capability-resolver first.
If capability status is not-supported or evidence is incomplete, return NO_CHANGE.
Ownership model
- Primary router owner:
github-ops-tree-router - Policy catalog owner:
github-ops-excellence - Delegates:
github-capability-resolvergithub-ticket-lifecycle-orchestratorgithub-projects-agile-linkagegithub-review-merge-admingithub-release-incident-flowgithub-ruleset-architecturegithub-actions-security-hardeningrepo-profile-governanceworkflow-self-anneal
Routing table
goal=ticket-lifecycle->github-ticket-lifecycle-orchestrator(+github-ops-excellencefor policy profile)goal=agile-projects->github-projects-agile-linkagegoal=review-merge->github-capability-resolver+github-review-merge-admingoal=release-incident->github-release-incident-flow(+github-ops-excellencefor policy profile)goal=repo-governance->repo-profile-governancegoal=actions-security->github-capability-resolver+github-actions-security-hardeninggoal=ruleset-architecture->github-capability-resolver+github-ruleset-architecturegoal=process-hardening->workflow-self-anneal
Required references
Output format
GITHUB_OPS_ROUTER_REPORT
goal: <ticket-lifecycle|agile-projects|review-merge|release-incident|repo-governance|actions-security|ruleset-architecture|process-hardening>
policy_profile: <strict|standard|light>
capability_resolution:
- required: <yes|no>
- status: <available-now|available-with-config-change|available-with-plan-upgrade|not-supported|not-run>
selected_skill_path:
- <ordered skills>
ownership:
- router: github-ops-tree-router
- policy_catalog: github-ops-excellence
- delegates: <skills>
checks:
- <required verifications>
decision:
- <apply|defer|NO_CHANGE>
missing_evidence:
- <none or artifacts>
What ships with it
5 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.
- 3d ago First seen · 77 lines · 27 tokens per session scan A bcefdf5269db
github-ops-tree-router is a skill published in the GitHub repository chf3198/copilot-governance (1 stars, last pushed 1mo ago), licensed MIT. It adds 27 tokens to every session and 715 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…