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 skills/coderifts/api-governance/api-governancenpx skills add coderifts/api-governance --skill api-governancegit clone --depth 1 https://github.com/coderifts/api-governanceWhat 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.00126 | $0.01081 |
| Opus 5 | $0.00063 | $0.00541 |
| Sonnet 5 | $0.00025 | $0.00216 |
| Haiku 4.5 | $0.00013 | $0.00108 |
Grade C, and why
api-governance scanned grade C with 1 finding 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- SOURCE OF TRUTH (do not hand-author tool names/descriptions or rule sentences): - Skill trigger description: agent-setup OpenAI/AGENTS rule body (coderifts-app src/agent-host-rule.js → scripts/generate-agent-host-fi How it starts
The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CodeRifts API Governance
Call preflight_change_set before merge, deploy, publish, or tool registration when a contract
artifact changed. No mutation of API/schema/contract surfaces without a valid authorize-path
receipt for the act you are about to perform. Branch on execution_action only.
When to use
- Merge, deploy, publish, or tool registration when a contract artifact changed (OpenAPI/Swagger, GraphQL, gRPC/protobuf, AsyncAPI, MCP manifest, or agent tool schemas).
- You hold a prior chain receipt and need authenticity/lifecycle only (
verify_receipt). - You need a past decision by id (
get_decision_details).
Do not use for a documentation-only change (README, guides, comments) with no contract artifact content change.
Tools
The coderifts MCP server (https://app.coderifts.com/mcp) exposes exactly three tools
(names from generated mcp.json — do not invent others):
-
preflight_change_set — Preflight a COMPLETE base→head change set of contract artifacts and return risk score and breaking-change analysis — plus, on the AUTHORIZE path only, a governance decision (ALLOW / WARN / REQUIRE_APPROVAL / BLOCK) and a signed chain-receipt when applicable. ANALYZE returns informational risk only: analysis_outcome, may_execute:false, no decision, no receipt.
Requires a pending base→head (before/after) contract change you are about to act on (merge, deploy, publish, or register tools). No pending change set → do not call this tool.
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 First seen · 89 lines · 126 tokens per session scan C 5fac6fab69dd
api-governance is a skill published in the GitHub repository coderifts/api-governance (0 stars, last pushed yesterday), licensed MIT. It adds 126 tokens to every session and 1,081 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
API Contract Validator
Validate API responses against OpenAPI/Swagger specifications, JSON Schema definitions, and consumer-driven contracts to prevent breaking changes.
detecting-shadow-api-endpoints
Discover and inventory shadow API endpoints that operate outside documented specifications using traffic analysis, code scanning, and API discovery platforms.
implementing-api-security-posture-management
Implement API Security Posture Management to continuously discover, classify, and score APIs based on risk while enforcing security policies across the API lifecycle.
backend-api-versioning
Use this skill when the user says 'API versioning', 'version strategy', 'URI versioning', 'header versioning', 'content negotiation', 'accept header', 'breaking change', 'API migration', 'deprecate endpoint', 'sunset endpoint'. This skill manages API version transitions using URI, header, or content-negotiation…
Breaking Change Detector
Compares two versions of a codebase or API and flags all breaking changes with migration hints.
Migration Guide Writer
Writes clear migration guides for library upgrades, breaking API changes, or framework version bumps.