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-collaborator-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-collaborator-execution)<a href="https://agentmods.dev/skills/chf3198/copilot-governance/role-collaborator-execution"><img src="https://agentmods.dev/badge/skills/chf3198/copilot-governance/role-collaborator-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.00870 |
| Opus 5 | $0.00010 | $0.00435 |
| Sonnet 5 | $0.00004 | $0.00174 |
| Haiku 4.5 | $0.00002 | $0.00087 |
Grade A, and why
role-collaborator-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 7d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role: Collaborator Execution
Responsibilities
- Implement only manager-scoped changes.
- Keep edits minimal and localized.
- Run required validation gates and capture outcomes.
- Update docs/changelog when behavior changes.
Upstream verification (from Manager)
Before implementing, verify Manager's scope:
- Are acceptance criteria testable and complete (binary pass/fail)?
- Are constraints realistic given available resources?
- Are verification gates achievable? If not, push back early.
- If scope is vague, request
MANAGER_HANDOFFrevision.
Entry criteria
- Valid
MANAGER_HANDOFFexists. - Required gates are defined.
- Active GitHub issue linked to work.
Branch and commit rules
- Create branch:
<type>/<issue#>-<slug>(e.g.,feat/62-baton-redesign). - Every commit references
#Nin message. - Pull latest
maininto branch before PR:git pull origin main. - Research tickets: no branch — post findings as ticket comment.
Exit criteria
COLLABORATOR_HANDOFFincludes concrete validation evidence.COLLABORATOR_HANDOFFexplicitly enumeratesadmin_required_ops.- Do not declare complete at exit; "all gates pass" = validated, not released.
- Any scope drift is explicitly flagged for manager re-handoff.
Rich comment template
COLLABORATOR_HANDOFF comment must include:
- Changes: per-file summary of what changed and why
- Behavior delta: before/after description of observable behavior
- AC evidence: each AC checkbox ✅ with the test command or output proving it
- Risks for Admin: potential CI flags, merge conflict risk, env dependencies
- Visualization (optional): Mermaid diagram or ASCII flow for complex changes
Add 🔧 reaction: gh api repos/{owner}/{repo}/issues/{N}/reactions -f content=wrench
Multi-ticket TODO model
When multiple tickets are in status:todo, the Collaborator:
- Holds ALL of them in TODO simultaneously (visible in baton map).
- Keeps exactly one in
status:in-progressat a time. - Completes and emits
COLLABORATOR_HANDOFFbefore pulling the next ticket toin-progress.
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.
- 7d ago First seen · 100 lines · 20 tokens per session scan A 118c8b35097a
role-collaborator-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 870 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.
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…
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…
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…