Agent skill · product strategy · github
agent-governance
Patterns and techniques for adding governance, safety, and trust controls to AI agent systems. Use this skill when: - Building AI agents that call external tools (APIs, databases, file systems) - Implementing policy-based access controls for agent tool usage - Adding semantic intent classification to detect dangerous prompts - Creating trust scoring systems for multi-agent workflows - Building audit trails for agent actions and decisions - Enforcing rate limits, content filters, or tool restrictions on agents - Working with any agent framework (PydanticAI, CrewAI, OpenAI Agents, LangChain, AutoGen)
Why this skill is useful
Provides domain-specific governance patterns and policy implementations for AI agents that enhance safety and compliance.
What it needs
About 8k tokens when loaded. Last updated 2026-08-07. 37,534 stars on the source repository.
What this skill does
Agent Governance Patterns Patterns for adding safety, trust, and policy enforcement to AI agent systems. Overview Governance patterns ensure AI agents operate within defined boundaries — controlling which tools they can call, what content they can process, how much they can do, and maintaining accountability through audit trails. When to Use Agents with tool access: Any agent that calls external tools (APIs, databases, shell commands) Multi-agent systems: Agents delegating to other agents need trust boundaries Production deployments: Compliance, audit, and safety requirements Sensitive operations: Financial transactions, data access, infrastructure management --- Pattern 1: Governance Policy Define what an agent is allowed to do as a composable, serializable policy object. Policy Composition Combine multiple policies (e.g., org-wide + team + agent-specific): Policy as YAML Store policies as configuration, not code: --- Pattern 2: Semantic Intent Classification Detect dangerous intent in prompts before they reach the agent, using pattern-based signals. Key insight: Intent classification happens before tool execution, acting as a pre-flight safety check. This is fundamentally different from output guardrails which only check after generation. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills github/agent-governance