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-excellencenpx skills add chf3198/copilot-governance --skill github-ops-excellencegit 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-excellence)<a href="https://agentmods.dev/skills/chf3198/copilot-governance/github-ops-excellence"><img src="https://agentmods.dev/badge/skills/chf3198/copilot-governance/github-ops-excellence.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.00036 | $0.01531 |
| Opus 5 | $0.00018 | $0.00766 |
| Sonnet 5 | $0.00007 | $0.00306 |
| Haiku 4.5 | $0.00004 | $0.00153 |
Grade A, and why
github-ops-excellence 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 — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Ops Excellence
Purpose
Provide a bounded, auditable policy and control catalog for high-quality GitHub execution across repositories.
Hard constraints
- No unbounded loops or recursive retries.
- Maximum one full pass per invocation.
- Maximum ten actionable recommendations per invocation.
- No silent policy changes; propose changes with rationale.
- No bypass escalation without explicit approval trail.
- If required evidence is missing, return
NO_CHANGEwith missing artifacts.
Modes
triage: issue quality and planning readiness.refinement: backlog readiness and dependency hygiene.pre-pr: branch hygiene and PR preparation.pre-merge: review/check/ruleset merge readiness.sprint-health: flow health, WIP risk, and review throughput.release-readiness: release gate and rollback readiness.incident-flow: containment-to-follow-up issue flow during production incidents.admin-audit: governance/ruleset/admin posture review.
Scope boundary (catalog ownership)
This skill is the policy catalog owner, not the primary executor.
Primary execution belongs to specialist skills selected by github-ops-tree-router.
This skill provides:
- policy-profile calibration (
strict|standard|light) - shared control definitions
- severity and verification standards
- conflict resolution guidance when specialists disagree
This skill is not the primary owner for repository profile/discoverability hygiene
(topics, homepage, social preview, community health file completeness). Delegate those to repo-profile-governance.
Invocation order
- For plan/feature-sensitive controls, run
github-capability-resolverfirst. - Run
github-ops-tree-routerto select execution skill(s). - Apply
github-ops-excellenceas profile overlay to calibrate strictness and evidence requirements.
Shared control packs by mode
triage
- Issue title is a plain imperative sentence ≤72 chars — no
type(scope):prefix (Conventional Commits belongs on commits/PRs, not issues). - Issue title has no pseudo-prefixes (
[BUG],[P1],TICKET-123,JIRA-123) and does not duplicate type in the title when atype:*label exists. - GitHub
#Nis used as canonical ID; no parallel local ID schemes (TICKET-NNN, bracket tags, etc.) present. - Issue includes: problem, expected outcome, acceptance criteria.
- Metadata includes: assignee, labels (priority + area + type), milestone/iteration, project link.
- Large work is decomposed with sub-issues/dependencies.
- Template/form adherence is verified;
blank_issues_enabled: falseconfirmed in repo.
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.
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 · 193 lines · 36 tokens per session scan A 81c751a5037a
github-ops-excellence is a skill published in the GitHub repository chf3198/copilot-governance (1 stars, last pushed 1mo ago), licensed MIT. It adds 36 tokens to every session and 1,531 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.
Other skills, from other repositories
release
Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.
release-notes
Draft concise release notes.
greptimedb-release
Runbook for publishing a new GreptimeDB version (tag + GitHub release + docs release-note PR) on the upstream GreptimeTeam/greptimedb repo. Use when asked to "release" / "publish" a GreptimeDB version (e.g. v1.1.0, v1.0.3).
refresh-arm-sdk-release
WORKFLOW SKILL — Prepares Azure.ResourceManager SDK refresh pull requests in azure-sdk-for-net. WHEN: "prepare sdk refresh", "refresh Azure.ResourceManager package", "update ARM SDK from autorest tag", "refresh changelog dependencies". INVOKES: git and GitHub pull request tools for branch, commit, push, and PR…
store-update
在 CCX Desktop 发布后下载 Store MSIX 并生成发布公告。用户提到 Store 上架、MSIX、从 GitHub Release 下载 store.msix、发布后同步 Windows Store、从 release 填写商店更新内容时必须使用此技能。该技能会下载最新 GitHub Release 的 amd64/arm64 MSIX，校验 sha256，从 Release body 生成 Store listing releaseNotes 预览，并输出手动上传指引。.
publish-registry
Publish @agentos-software/ registry packages from AgentOS. Use whenever the user asks to publish or release registry software/agent packages.