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 anotb/management-consulting-plugin --skill project-governancegit clone --depth 1 https://github.com/anotb/management-consulting-pluginWrote 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/anotb/management-consulting-plugin/project-governance)<a href="https://agentmods.dev/skills/anotb/management-consulting-plugin/project-governance"><img src="https://agentmods.dev/badge/skills/anotb/management-consulting-plugin/project-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/anotb/management-consulting-plugin/project-governance"><img src="https://agentmods.dev/badge/skills/anotb/management-consulting-plugin/project-governance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00053 | $0.00737 |
| Opus 5 | $0.00026 | $0.00368 |
| Sonnet 5 | $0.00011 | $0.00147 |
| Haiku 4.5 | $0.00005 | $0.00074 |
Grade A, and why
project-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 yesterday.
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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Governance
Give the client timely decisions and visibility into delivery. Use the lightest governance that meets the engagement's risk, complexity, and mandatory controls. Start from the client's existing PMO templates, contract, decision rights, and reporting rhythm.
Use available scope, budget, team, milestones, and reporting evidence. Mark missing facts and proposed roles instead of inventing names or approvals. Complete useful draft governance without waiting for charter sign-off; distinguish a proposal from authority to spend, deploy, or change the engagement.
Establish authority and cadence
A small advisory engagement may need a sponsor, engagement lead, decision log, and short check-in. A transformation may need workstream forums, a program review, and a steering committee. Add a forum only when it makes a decision, resolves a dependency, or satisfies an identified requirement.
For consequential decisions, record the decider, required input or approval, deadline, escalation path, and evidence needed. Distinguish the consultant's internal recommendation review from the client's decision to invest or implement. If the user supplies joint approvals or regulated authorities, preserve them explicitly.
Use RACI when it clarifies delivery responsibility. Normally assign one accountable role per deliverable and at least one responsible role; the same person may be both. Record assignments as proposed until confirmed. Keep roles current when ownership changes.
Report the state of delivery
Lead with the overall assessment, the decision or intervention needed, and when it becomes time-critical. Separate baseline, current forecast, and approved changes. Report outcomes completed, remaining work, milestones, cost, resource constraints, and material dependencies at the requested depth.
Show RAG status with definitions and trend. Use Unknown where evidence is missing; do not convert missing information into Green. Base progress on delivered scope or a defensible measure of remaining effort. Compare spending to planned and earned progress with the cost curve in view; early front-loaded expenditure alone does not prove overrun.
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.
- yesterday Changed · -262 lines · -64 tokens per session c8427d1fbec5
- 9d ago First seen · 306 lines · 117 tokens per session scan A 9221de4b7464
project-governance is a skill published in the GitHub repository anotb/management-consulting-plugin (51 stars, last pushed 3d ago), licensed MIT. It adds 53 tokens to every session and 737 once invoked, about $0.0003 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-30.
Other skills, from other repositories
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
meeting-action-items
Turn meeting notes into cited decisions, owners, tickets.
track-management
Use this skill when creating, managing, or working with Conductor tracks - the logical work units for features, bugs, and refactors. Applies to spec.md, plan.md, and track lifecycle operations.
stakeholder-communication
Communicate effectively with stakeholders across functions and seniority levels. Use this skill when writing status updates, preparing executive reviews, sharing technical decisions with non-technical audiences, managing up, communicating bad news, or designing the communication cadence for a project. Triggers on…
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.
create-stories
Break a single epic into implementable story files. Reads the epic, its GDD, governing ADRs, and control manifest. Each story embeds its GDD requirement TR-ID, ADR guidance, acceptance criteria, story type, and test evidence path. Run after /create-epics for each epic.