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-ticket-lifecycle-orchestratornpx skills add chf3198/copilot-governance --skill github-ticket-lifecycle-orchestratorgit 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-ticket-lifecycle-orchestrator)<a href="https://agentmods.dev/skills/chf3198/copilot-governance/github-ticket-lifecycle-orchestrator"><img src="https://agentmods.dev/badge/skills/chf3198/copilot-governance/github-ticket-lifecycle-orchestrator.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.00027 | $0.00689 |
| Opus 5 | $0.00014 | $0.00345 |
| Sonnet 5 | $0.00005 | $0.00138 |
| Haiku 4.5 | $0.00003 | $0.00069 |
Grade A, and why
github-ticket-lifecycle-orchestrator 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 5d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Ticket Lifecycle Orchestrator
Hard constraints
- No unbounded loops. Max one lifecycle pass per invocation.
- If required evidence is missing, return
NO_CHANGEwith missing artifacts. - Do not claim merge/closeout success without verification evidence.
Issue title format — plain imperative
<Imperative verb phrase describing the desired outcome> [≤ 72 chars]
- Start with imperative verb: "Fix", "Add", "Normalize", "Audit", "Stabilize"
- Plain English, human-scannable in boards and notifications
- No
type(scope):prefix — type/scope expressed via labels - No bracket tags
[BUG], no parallel IDsTICKET-NNN
Good: Fix header nav contrast on dark hero backgrounds
Bad: fix(nav): fix header nav contrastTICKET-008: Fix header
Commit and PR title format — Conventional Commits
<type>(<scope>): <imperative description> [≤ 72 chars]
Types: feat fix chore content perf refactor docs style test
Branch naming
<type>/<issue-number>-<short-slug> — e.g. fix/5-nav-contrast, feat/11-footer-redesign
Template requirements
Every repo must have .github/ISSUE_TEMPLATE/ with at minimum: bug, task, epic forms.
Config: blank_issues_enabled: false. Plus PULL_REQUEST_TEMPLATE.md with issue linkage.
Phase protocol (compact)
| Phase | Key actions |
|---|---|
| intake | Validate issue, apply labels/priority/milestone |
| planning | Split to sub-issues, add dependencies, set project fields |
| execution | One branch per ticket, link in Development panel, atomic commits |
| pre-pr | PR links issue with closing keywords, test evidence attached |
| review | Resolve feedback, re-run checks after changes |
| merge | Required reviews/checks satisfied, merge per repo policy |
| closeout | Issue state transition, branch deletion, post-merge cleanup |
Label taxonomy reference
See manager-ticket-lifecycle for full label taxonomy:
type:*, status:*, priority:*, area:*, role:*
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.
- 5d ago First seen · 79 lines · 27 tokens per session scan A b902c05e4aad
github-ticket-lifecycle-orchestrator is a skill published in the GitHub repository chf3198/copilot-governance (1 stars, last pushed 1mo ago), licensed MIT. It adds 27 tokens to every session and 689 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-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
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…