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 manager-ticket-lifecyclegit 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/manager-ticket-lifecycle)<a href="https://agentmods.dev/skills/chf3198/copilot-governance/manager-ticket-lifecycle"><img src="https://agentmods.dev/badge/skills/chf3198/copilot-governance/manager-ticket-lifecycle.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.00032 | $0.00850 |
| Opus 5 | $0.00016 | $0.00425 |
| Sonnet 5 | $0.00006 | $0.00170 |
| Haiku 4.5 | $0.00003 | $0.00085 |
Grade A, and why
manager-ticket-lifecycle 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ticket-as-Baton Lifecycle
Core paradigm
The GitHub issue is the baton. It carries work through Manager → Collaborator → Admin → Consultant. Each role writes a structured comment on the ticket and transitions the status label — mirroring a Jira card moving across a Scrum board.
Status workflow (label transitions)
backlog → ready → in-progress → review → done
(create) (scope) (implement) (PR/ops) (close)
Label taxonomy
- Type:
type:epic|story|task|bug|doc|research - Status:
status:backlog|ready|in-progress|review|done - Priority:
priority:P1|P2|P3 - Area:
area:dashboard|hooks|skills|instructions|agents|scripts|infra - Role (current holder):
role:manager|collaborator|admin|consultant
Manager creates ticket
gh issue create --title "<imperative>" --label "type:..." --label "status:backlog" --label "priority:..." --label "area:..."- Body: description, acceptance criteria, story points, parent epic ref.
- Add scope comment (see role-manager-execution output contract).
- Transition:
status:backlog→status:ready, setrole:manager. - Emit
MANAGER_HANDOFFwithissue: #N. - Swap label:
role:manager→role:collaborator.
Epic decomposition
For large work, create Epic issue, then sub-issues referencing parent. Each sub-issue gets its own label set and full lifecycle.
Parallel dispatch protocol
Manager assigns independent tickets to different collaborators:
- Research → Rex Research (web search, analysis)
- Code impl → Cody Builder (features, fixes)
- UI/CSS → Dash Styles (visual, layout)
- Docs → Petra Prose (technical writing) All assigned tickets execute concurrently. Each has its own baton.
Research ticket lifecycle
Research tickets use the full baton but skip branching:
- No branch created — research produces findings, not code.
- Collaborator posts research findings as ticket comment.
- Admin reviews wiki/research/ storage — no merge needed.
- Consultant validates research quality and wiki placement.
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 · 88 lines · 32 tokens per session scan A 9fa5e52b7307
manager-ticket-lifecycle is a skill published in the GitHub repository chf3198/copilot-governance (1 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 850 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
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the stepfun-37 smoke test), open code review (ocr), PR…
cyrus-setup-repository
Add one or more Git repositories to Cyrus configuration so it can process issues from those repos.
github-sync
Bidirectional synchronization of epics and tasks with GitHub issues, labels, and relationships.
github-sync-helper
General GitHub basic operations + automation for GitHub platform objects (Issues/Labels/Milestones/Releases/Actions) in the Minis environment. This skill must be triggered when the user mentions any basic Git/GitHub operation or workflow, including "how to use GitHub," clone, init, remote, branch, commit, push, pull…