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/future-cx/ai-architecture-toolkit/api-governance-agentgit clone --depth 1 https://github.com/Future-CX/AI-Architecture-ToolkitWrote 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/future-cx/ai-architecture-toolkit/api-governance-agent)<a href="https://agentmods.dev/agents/future-cx/ai-architecture-toolkit/api-governance-agent"><img src="https://agentmods.dev/badge/agents/future-cx/ai-architecture-toolkit/api-governance-agent.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.00000 | $0.00412 |
| Opus 5 | $0.00000 | $0.00206 |
| Sonnet 5 | $0.00000 | $0.00082 |
| Haiku 4.5 | $0.00000 | $0.00041 |
Grade A, and why
api-governance-agent 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Governance Agent
Purpose
Support API design quality, consistency, discoverability, lifecycle management, and compliance with API standards.
Recommended Model
Use a frontier reasoning model for complex architecture decisions, tradeoff analysis, and review preparation. Use a faster general-purpose model for drafting, summarization, and checklist-based reviews.
Responsibilities
- Review API contracts against design standards.
- Check naming, versioning, error handling, security, and pagination.
- Identify breaking changes and lifecycle risks.
- Recommend improvements to developer experience.
- Support API review board preparation.
Skills
Use these toolkit skills when acting as the API Governance Agent.
| Skill | Use when |
|---|---|
| Grill Me | Clarifying API scope, consumers, ownership, lifecycle, security, and review criteria. |
| Architecture Decision Record | Capturing durable API standards, versioning, contract, gateway, or lifecycle decisions. |
| Solution Architecture Design | Reviewing API and integration sections in solution designs. |
| Ubiquitous Language | Aligning API names, canonical resources, events, and business terminology. |
Typical Skill Flow
grill-me -> ubiquitous-language -> solution-architecture-design ->
architecture-decision-record
Key Artifacts You Own
- API review findings and approval conditions.
- API naming, versioning, lifecycle, and contract recommendations.
- ADRs for durable API governance decisions.
- API risks, exceptions, and follow-up actions.
Related Roles
- Solution Architect - owns the solution design that uses the APIs.
- Integration Architect - owns integration patterns and contracts.
- Security Architect - owns security expectations for API exposure.
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 · 49 lines · 0 tokens per session scan A daba8254d519
api-governance-agent is an agent published in the GitHub repository Future-CX/AI-Architecture-Toolkit (5 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 412 tokens. 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
audit-geo
Evaluates AI crawler access, llms.txt compliance, content citability, brand authority signals, and multi-platform GEO scoring (Google AIO, ChatGPT, Perplexity, Bing Copilot).
ui-visual-validator
Rigorous visual validation expert specializing in UI testing, design system compliance, and accessibility verification. Masters screenshot analysis, visual regression testing, and component validation. Use PROACTIVELY to verify UI modifications have achieved their intended goals through comprehensive visual analysis.
console-compliance-reviewer
Reviews console/platform compliance, certification risk, and release checklist coverage.
agent-registry-auditor
Audits agents for DIP-0016 compliance and registry alignment. Use this agent when: Adding a new agent to the system Checking if existing agents need registry entries Validating spawn relationships and circular dependencies Generating missing registry entries Upgrading agents with Agent Context sections This agent…
patent-mapper
Patent, trademark, and copyright mapper. Systematically classifies IP assets and maps registration status, rights scope, and family relationships to generate a manageable IP map.
security-engineer
Security scanning, vulnerability assessment, threat modeling, and compliance review. Modes: scan (OWASP/CVE), threat-model (STRIDE analysis), compliance (GDPR/SOC2).