00-governance

A set of baseline rules for governing a coding-agent workflow and its documentation.

In plain words
What is it for?
It is for organizing skills, agents, plans, documentation, and version-control practices across projects.
Why use it?
It keeps workflow instructions in agreed locations, prevents unsupported command formats, and keeps plans and progress records consistent.

Cursor rule

Install

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.

agentmods
npx agentmods add rules/joaonic/agentkit/00-governance
Clone the repo
git clone --depth 1 https://github.com/Joaonic/agentkit
Per session 138 This file is loaded in full into every session.
When invoked 138 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00138 $0.00138
Opus 5 $0.00069 $0.00069
Sonnet 5 $0.00028 $0.00028
Haiku 4.5 $0.00014 $0.00014

Measured yesterday against content hash e5c449acc076, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

00-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.

src/core/rules/00-governance.mdc · 19 lines

What it actually says

Governance Baseline

Mandatory:

  • Canonical governance lives in docs/governance/cursor.
  • Skills and agents only. Do not create .cursor/commands.
  • Do not use slash-style invocation notation in docs, rules, skills, or agents.
  • Keep plan files in .cursor/plans and keep status synchronized with real progress.
  • Use AGENTS.md as operational index for roles and quality gates.

VCS policy:

  • Default is GitLab-first with glab.
  • Exception: web/your-github-project uses GitHub with gh.
Changes

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.

  1. yesterday First seen · 19 lines · 138 tokens per session scan A e5c449acc076

Subscribe to this mod's changes

00-governance is a cursor rule published in the GitHub repository Joaonic/agentkit (2 stars, last pushed 3mo ago), licensed MIT. It adds 138 tokens to every session, about $0.0007 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.