claude-governance / plugin
AGENTS.md4 starsChanged 6 months agoMITView on GitHub
This is your install + operating protocol. Claude Code reads ./CLAUDE.md automatically. Codex and other agents should start here. claude-governance is a governance plugin for AI-assisted development. It ships Markdown skills, shell hooks for Claude Code, examples, ADRs, and compliance references. The Codex package exposes the skills and repository guidance; Claude Code-specific hooks remain Claude-only until Codex supports equivalent plugin hooks. Skills are guidance that an agent executes under the user's authority. Claude Code hooks provide local enforcement for Claude…
In this repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- plugin/CLAUDE.mdCLAUDE.md
- create-adrSkill
- eu-ai-act-checkSkill
- governance-checkSkill
- governance-setupSkill
- iso-42001-checkSkill
- spec-driven-devSkill
The file
Files
Agents working on claude-governance
This is your install + operating protocol. Claude Code reads ./CLAUDE.md automatically. Codex and other agents should start here.
What this is
claude-governance is a governance plugin for AI-assisted development. It ships Markdown skills, shell hooks for Claude Code, examples, ADRs, and compliance references. The Codex package exposes the skills and repository guidance; Claude Code-specific hooks remain Claude-only until Codex supports equivalent plugin hooks.
Install
- Claude Code:
claude plugin marketplace add pitimon/claude-governance && claude plugin install claude-governance@claude-governance - Codex:
codex plugin marketplace add pitimon/claude-governance && codex plugin add claude-governance@pitimon-claude-governance - Codex refresh if already added:
codex plugin marketplace upgrade pitimon-claude-governance
Read this order
./AGENTS.md- cross-agent install and operating protocol../CLAUDE.md- architecture reference and Claude Code-specific hook behavior../README.md- user-facing overview, workflows, and project structure.- The relevant
skills/<name>/SKILL.mdfor the user's request.
Trust boundary
Skills are guidance that an agent executes under the user's authority. Claude Code hooks provide local enforcement for Claude Code only. In Codex, use the skills as explicit checklists and workflows; do not assume hooks/session-start.sh or hooks/secret-scanner.sh are automatically active. Note that Codex still parses hooks/hooks.json at install with a strict schema (top level = hooks only — see issue #51), so that file must stay schema-pure even though Codex does not run the hooks.
PowerShell ports (hooks/secret-scanner.ps1, hooks/session-start.ps1) exist for Claude Code on native Windows without Git Bash; they are verified equivalent to the .sh hooks on a windows-latest CI job. Codex does not run them either. See the Platform Support table in README.md.
Common tasks
- "Check this before commit" ->
skills/governance-check/SKILL.md - "Record why we chose this architecture" ->
skills/create-adr/SKILL.md - "Plan this feature before coding" ->
skills/spec-driven-dev/SKILL.md - "Set up governance in this repo" ->
skills/governance-setup/SKILL.md - "Check EU AI Act readiness" ->
skills/eu-ai-act-check/SKILL.md - "Check ISO 42001 readiness" ->
skills/iso-42001-check/SKILL.md
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

