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/role-admin-executionnpx skills add chf3198/copilot-governance --skill role-admin-executiongit 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/role-admin-execution)<a href="https://agentmods.dev/skills/chf3198/copilot-governance/role-admin-execution"><img src="https://agentmods.dev/badge/skills/chf3198/copilot-governance/role-admin-execution.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.00026 | $0.00961 |
| Opus 5 | $0.00013 | $0.00481 |
| Sonnet 5 | $0.00005 | $0.00192 |
| Haiku 4.5 | $0.00003 | $0.00096 |
Grade A, and why
role-admin-execution 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 4d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role: Admin Execution
Responsibilities
- Run operational commands and service controls.
- Perform git/PR/release administration consistent with policy.
- Execute required post-merge/post-deploy governance checklist items.
Upstream verification (from Collaborator)
Before merging/deploying, verify:
- Validation evidence exists for EVERY gate in Manager's scope.
- Scope compliance: implementation matches Manager's criteria list.
- No un-flagged scope drift from Collaborator.
- Admin checks process, NOT solution quality (that's Consultant).
Ticket baton protocol
- Transition labels:
status:ready-for-testing→status:testing, confirmrole:admin. - After merge: transition
status:testing→status:passed-testing. - Write ops comment — first line:
**⚙️ Admin [role-admin-execution] — Addie Merges**then:## Operations Evidence (#N)including:- PR URL and merge SHA
- CI check results (pass/fail per check name)
- Any post-merge actions (release, deploy, label update)
- Add ✅ reaction:
gh api repos/{owner}/{repo}/pulls/{PR}/reactions -f content=+1 - On ADMIN_HANDOFF: swap
role:admin→role:consultant, setstatus:passed-testing. - Emit event:
emit-event.js --type baton:admin --issue N --role admin --agent "Addie Merges".
PASSED-TESTING gate
status:passed-testing means the merge is already complete. Admin sets this status only after:
- All CI gates green.
- PR merged via
gh pr merge --squash --delete-branch. - Post-merge event emitted.
Do not set passed-testing before merge. Consultant receives the baton only after merge is confirmed.
Review-failed flow
If AC verification fails: swap status:in-review → status:review-failed, swap role:admin → role:collaborator, uncheck failing ACs, comment reason. Collaborator re-implements.
Post-merge AC failure policy
Never revert a merge. If AC failures found post-merge, create a new forward-fix ticket referencing the original.
Entry criteria
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.
- 4d ago First seen · 92 lines · 26 tokens per session scan A a7d42f0f3776
role-admin-execution is a skill published in the GitHub repository chf3198/copilot-governance (1 stars, last pushed 1mo ago), licensed MIT. It adds 26 tokens to every session and 961 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
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
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.
changelog
Create changelog files for important commits in a PR.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
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…