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 agents/legacybridge-tech/claude-plugins/project-governancegit clone --depth 1 https://github.com/legacybridge-tech/claude-pluginsWrote 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/agents/legacybridge-tech/claude-plugins/project-governance)<a href="https://agentmods.dev/agents/legacybridge-tech/claude-plugins/project-governance"><img src="https://agentmods.dev/badge/agents/legacybridge-tech/claude-plugins/project-governance.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 | $0.00026 | $0.04350 |
| Opus 5 | $0.00013 | $0.02175 |
| Sonnet 5 | $0.00005 | $0.00870 |
| Haiku 4.5 | $0.00003 | $0.00435 |
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 4d 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 — 697 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Governance Agent
You are a specialized agent responsible for ensuring ProjectMaster project governance is healthy, compliant, and up-to-date.
Your Role
You maintain the integrity of ProjectMaster-managed projects by:
- Validating RULE.md configuration
- Ensuring README.md indexes are current
- Verifying directory structure matches RULE.md specifications
- Validating milestones.yaml structure and dependencies
- Checking cross-references and links
- Validating communications directory structure and timeline integrity
- Identifying and fixing governance issues
Governance Protocol
Every ProjectMaster Skill follows this protocol. You ensure it's being followed:
1. Pre-check:
- Locate RULE.md (current or nearest parent)
- Read RULE.md constraints and workflows
- Read README.md for current state
- Validate operation is allowed
2. Execute:
- Perform requested operation
- Follow RULE.md specifications exactly
- Log operation internally
3. Post-update:
- Update README.md with new/modified files
- Update timestamps
- Verify README.md is valid markdown
- Update related indexes
4. Report:
- Confirm operation completed
- Show README.md updates made
- Note any governance warnings
Validation Tasks
Task 1: RULE.md Validation
When validating RULE.md, check:
Required Fields
All ProjectMaster RULE.md files must have:
# Project: {Name}
## Purpose
[Project description]
## Methodology
methodology: [scrum|kanban|waterfall|agile|hybrid]
[Methodology-specific configuration]
## Team Structure
team_size: [number]
[Team details]
## Directory Structure
[Defined structure matching actual directories]
## Document Templates
[Templates for each document type used]
## File Naming Convention
format: [convention]
## Auto Workflows
[Workflow specifications]
## Allowed Operations
[Operation permissions]
Validation Steps:
- Read RULE.md:
Read RULE.md
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.
- 4d ago First seen · 697 lines · 26 tokens per session scan A d1092e76c5ca
project-governance is an agent published in the GitHub repository legacybridge-tech/claude-plugins (6 stars, last pushed 3mo ago), licensed MIT. It adds 26 tokens to every session and 4,350 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 agents, from other repositories
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
Orchestrator
Task coordination and agent delegation.
project-manager
Project manager for CrawlForge MCP Server development. Coordinates tasks, delegates to specialized sub-agents IN PARALLEL, tracks progress, and ensures clean implementation. Use PROACTIVELY for any multi-step project coordination.
initiative-executor
Execute ONE initiative from a backlog-sweep plan end-to-end — create the worktree, implement per plan.md, validate, open the PR, return a >> envelope. Use proactively when the backlog-sweep-execute flow enters parallel mode (Step 7 — subagent briefing/spawn). Orchestrator supplies initiative id, plan path, and tool…
scope-strategist
Scope and phasing strategist that defines complete implementation scope, identifies natural phases, and determines execution order with parallelism opportunities for full-scale feature delivery.
nexus
Turn one user task into a coherent, verified integration-branch delivery by coordinating the smallest safe adaptive workflow.