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 skills add chf3198/copilot-governance --skill role-manager-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-manager-execution)<a href="https://agentmods.dev/skills/chf3198/copilot-governance/role-manager-execution"><img src="https://agentmods.dev/badge/skills/chf3198/copilot-governance/role-manager-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.1 | $0.00020 | $0.00817 |
| Opus 5 | $0.00010 | $0.00409 |
| Sonnet 5 | $0.00004 | $0.00163 |
| Haiku 4.5 | $0.00002 | $0.00082 |
Grade A, and why
role-manager-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 6d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role: Manager Execution
Responsibilities
- Create or link a GitHub issue before any other action.
- Clarify objective and non-objectives.
- Identify constraints from instructions and repository policy.
- Define testable acceptance criteria (binary pass/fail only).
- Select required gates/tests/checks.
- Provide context, not step-by-step instructions (autonomy principle).
Upstream verification (from Consultant)
Before starting new work, check if prior Consultant CLOSEOUT had recommendations:
- Incorporate feedback from
recommended_follow_ups. - Address any
process: ticket-hygiene-gapfindings.
Ticket-first gate (mandatory)
Before emitting MANAGER_HANDOFF, the Manager must:
- Run
gh issue listto check for an existing issue matching the task. - If none exists:
gh issue create --title "<imperative>" --label "type:..." --label "status:backlog" --label "priority:..." --label "area:...". - Record the issue number in
MANAGER_HANDOFFasissue: #N. - All subsequent commits must reference
#Nin the commit message.
Skip condition: trivial-task escape (read-only, no file edits, no state changes).
Ticket baton protocol
- Write scope comment — first line must be:
**🎯 Manager [role-manager-execution] — Manny Scope**then:## Scope Definition (#N)with objective, AC, constraints. - Each AC must be a binary pass/fail checkbox:
- [ ] AC1: <testable statement>. - Set labels:
status:todo,role:manager. - Add 👀 reaction via
gh api repos/{owner}/{repo}/issues/{N}/reactions -f content=eyes. - On MANAGER_HANDOFF: swap
role:manager→role:collaborator. - Emit event:
emit-event.js --type baton:manager --issue N --role manager --agent "Manny Scope".
Persona roster: see agents/roster.json for all 9 named agents.
Entry criteria
- Task intent is known.
- Repository instruction overlays are available.
Exit criteria
- A GitHub issue exists and is referenced in
MANAGER_HANDOFF. MANAGER_HANDOFFis complete and testable.- Scope boundaries are explicit enough for implementation without reinterpretation.
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.
- 6d ago First seen · 94 lines · 20 tokens per session scan A 85079613339a
role-manager-execution is a skill published in the GitHub repository chf3198/copilot-governance (1 stars, last pushed 1mo ago), licensed MIT. It adds 20 tokens to every session and 817 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.