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 vladm3105/aidoc-flow-framework --skill ucx-github-governancegit clone --depth 1 https://github.com/vladm3105/aidoc-flow-frameworkWrote 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/vladm3105/aidoc-flow-framework/ucx-github-governance)<a href="https://agentmods.dev/skills/vladm3105/aidoc-flow-framework/ucx-github-governance"><img src="https://agentmods.dev/badge/skills/vladm3105/aidoc-flow-framework/ucx-github-governance/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/vladm3105/aidoc-flow-framework/ucx-github-governance"><img src="https://agentmods.dev/badge/skills/vladm3105/aidoc-flow-framework/ucx-github-governance.svg" alt="Reviewed on agentmods" width="80" 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.00043 | $0.00657 |
| Opus 5 | $0.00022 | $0.00329 |
| Sonnet 5 | $0.00009 | $0.00131 |
| Haiku 4.5 | $0.00004 | $0.00066 |
Grade A, and why
ucx-github-governance 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UCX GitHub Governance Skill
Purpose
Manage issue->plan-set->PR governance flow in GitHub while preserving UCX V3 control-plane/execution-plane separation.
Canonical Label Flow
Use governance label progression exactly:
ai:ready -> ai:in-progress -> ai:review-requested
Rules:
- Only
ai:readyissues are eligible for autonomous execution. - Do not use
ai:approvedorai:rejected. - Transition to
ai:in-progressonly after required plan artifacts are approved. - Use
ai:review-requestedwhen acceptance criteria verification is complete and PR is ready for review.
Mandatory Issue Workflow
Before coding:
- Initialize project context when required (
sdd_init, thensdd_preflight). - Complete issue analysis.
- Create planning-first artifacts (layer roadmap, planning index, changelog plan).
- Review planning artifacts for gaps.
- Fix gaps or record explicit deferrals with rationale.
- Create required plan artifact(s): document-layer IPLAN and/or permanent development plan (
PLAN-NNN_*, preferred). - Review plan artifact(s) for step clarity and acceptance-criteria mapping.
- Record explicit plan approval (human reviewer or independent LLM-as-judge session).
- Start implementation by transitioning issue to
ai:in-progress.
Before review request:
- Verify linked-issue acceptance criteria with evidence.
- Update issue checkboxes based on verified evidence only.
- Add direct PR link (number + URL) to linked issue.
After review round:
- Post review outcomes back to linked issue.
- If re-review required, post delta findings and next actions.
Round-Based PR Governance (Mandatory)
For autonomous execution PRs, run two-round maximum gate policy:
sdd_validatesdd_reviewsdd_remediate- post-remediation
sdd_validate - Hermes final blocker-gap/inconsistency review
If Round 1 fails, run Round 2 with same sequence.
If Round 2 fails, mark escalation REQUIRED, block merge, require human review.
GitHub PR Policy
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 · 90 lines · 43 tokens per session scan A ac2807bb9e01
ucx-github-governance is a skill published in the GitHub repository vladm3105/aidoc-flow-framework (17 stars, last pushed today), licensed MIT. It adds 43 tokens to every session and 657 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-09-04.
Other skills, from other repositories
gsd-quick
Execute a quick task with GSD guarantees (atomic commits, state tracking) but skip optional agents.
gsd-quick-batch
Batch several /gsd:quick-shaped tasks together — planned, dispatched, and merged as one run.
gh-issues
Fetch GitHub issues, spawn sub-agents to implement fixes and open PRs, then monitor and address PR review comments. Usage: /gh-issues [owner/repo] [--label bug] [--limit 5] [--milestone v1.0] [--assignee @me] [--fork user/repo] [--watch] [--interval 5] [--reviews-only] [--cron] [--dry-run] [--model glm-5]…
gsd-pause-work
Create context handoff when pausing work mid-phase.
gsd-ship
Create PR, run review, and prepare for merge after verification passes.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.