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 jason21wc/ai-governance-mcp --skill pmogit clone --depth 1 https://github.com/jason21wc/ai-governance-mcpWrote 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/jason21wc/ai-governance-mcp/pmo)<a href="https://agentmods.dev/skills/jason21wc/ai-governance-mcp/pmo"><img src="https://agentmods.dev/badge/skills/jason21wc/ai-governance-mcp/pmo/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/jason21wc/ai-governance-mcp/pmo"><img src="https://agentmods.dev/badge/skills/jason21wc/ai-governance-mcp/pmo.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.00193 | $0.01231 |
| Opus 5.5 | $0.00077 | $0.00492 |
| Sonnet 5.5 | $0.00039 | $0.00246 |
| Haiku 4.5 | $0.00019 | $0.00123 |
Grade A, and why
pmo 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 2mo 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Runtime Context
After the skill loads, inspect the project root, top-level structure, and likely charter locations with ordinary read-only calls. No charter found is a valid result; distinguish it from paths that could not be inspected.
Instructions
This skill applies ONE lens — Purpose · Method · Outcomes — in one of two directions. It is the canonical home of that lens; a project's own filled-in charter lives in that project and points here for the method.
Every project that turns inputs into outputs has three latent layers:
- PURPOSE — who receives value, and why this beats their best alternative.
- METHOD — the mechanisms that produce the value (rules, pipelines, schemas, data sources, adjustments).
- OUTCOMES — the deliverable as its audience experiences it, plus how you know the purpose was actually delivered (the closed loop most frameworks omit).
Read procedure.md in this skill folder for the full protocol before running either mode.
Quick Start
- Collect the Runtime Context above and determine the mode + target.
- If the user said "charter" / "write a charter" / "capture this project's purpose" → charter mode (build). (For standing up a brand-new project from scratch, that's
/start-project, not this.) - If the user said "review" / "audit" / "does this deliver its purpose" → review mode.
- If they said "PMO" with no direction, ask which. If they named a project/path, use it; else use the current project.
- If the user said "charter" / "write a charter" / "capture this project's purpose" → charter mode (build). (For standing up a brand-new project from scratch, that's
- Read
procedure.mdfor the mode's phases. - Run the mode's phases in order (both start with a governance check).
- Deliver — a charter (charter mode) or a findings report (review mode).
The two modes
- Charter (build) — extract the project's Purpose, Method map, and Outcomes from what already exists, then write a ≤12-line charter block (template in
procedure.md) into the project. Pointers to method docs, never restatements; a "verified by" line is mandatory (a charter without it is decoration). - Review (audit) — run the four-direction traceability trace + the P/M/O/X checklist against the project, citing file-level evidence for every verdict, classify each gap into one of four classes, and report read-only with minimal proposed fixes. Fixes are governed separately.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2mo ago First seen · 60 lines · 193 tokens per session scan A ad3ab2d40aaf
pmo is a skill published in the GitHub repository jason21wc/ai-governance-mcp (0 stars, last pushed 25d ago), licensed Apache-2.0. It adds 193 tokens to every session and 1,231 once invoked, about $0.0008 per session on Opus 5.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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
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…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.