AI tool comparison
agent-skills vs Agent Governance Toolkit
Which one should you ship with? Here is the side-by-side panel verdict, pricing read, reviewer split, and community vote comparison.
Developer Tools
agent-skills
Production-grade engineering skills library for AI coding agents
75%
Panel ship
—
Community
Free
Entry
agent-skills is a structured library of 20 production-grade engineering skills for AI coding agents, published by Addy Osmani (former Google Chrome DevTools lead, author of Essential JavaScript Design Patterns). It provides a complete spec-to-ship workflow via 7 slash commands (/spec, /plan, /build, /test, /review, /code-simplify, /ship) that work across Claude Code, Cursor, Gemini CLI, Windsurf, and GitHub Copilot — any agent that supports CLAUDE.md or equivalent configuration files. The library includes three specialist personas that activate on demand: a security auditor (checks for injection vulnerabilities, hardcoded secrets, OWASP Top 10), a code reviewer (focuses on maintainability, complexity, and test coverage), and a test engineer (generates unit, integration, and edge-case tests). Four reference checklists (API design, accessibility, performance, deployment) give agents shared evaluation criteria. Each skill is written as a Markdown instruction file following the CLAUDE.md conventions popularized by the karpathy-skills library. agent-skills accumulated 6,693 GitHub stars in its first trending week, outpacing most comparable skill collections. Osmani's framing — treating agent skills as a first-class engineering asset rather than ad-hoc prompts — resonates with teams trying to standardize how they use AI coding tools. The library is MIT-licensed and designed to be forked and extended.
Developer Tools
Agent Governance Toolkit
Open-source runtime security for AI agents — covers all 10 OWASP agentic risks
75%
Panel ship
—
Community
Paid
Entry
Microsoft's Agent Governance Toolkit (AGT) is an open-source MIT-licensed library that brings runtime security governance to autonomous AI agents. Launched on April 2, 2026, it's the first toolkit to address all 10 items on the OWASP Agentic AI Top 10 with deterministic, sub-millisecond policy enforcement — without requiring any rewrite of existing agent code. The core architecture is a stateless policy engine called Agent OS that intercepts every agent action before execution at sub-1ms latency (p99 < 0.1ms). It hooks into native extension points: LangChain's callback handlers, CrewAI's task decorators, Google ADK's plugin system, and OpenAI Agents SDK middleware. Published adapters cover Python, TypeScript, Rust, Go, and .NET — plus integrations for LangGraph, Haystack, and PydanticAI. AGT covers zero-trust identity for agents, execution sandboxing, policy enforcement (EU AI Act, HIPAA, SOC2 mapping built-in), and SRE reliability patterns for agentic systems. Microsoft is actively working to move the project into a foundation (likely OWASP or Linux Foundation) for community governance. For any team shipping autonomous agents to production, this may be the most important open-source release of Q2 2026.
Reviewer scorecard
“Having security audits, test generation, and spec creation as first-class slash commands changes how you think about agent-assisted development. The cross-tool compatibility (Claude, Cursor, Gemini) means you can standardize across a team with mixed tool preferences. Fork it, customize the checklists, and you have a company playbook.”
“The zero-rewrite integration is the killer feature — hooking into LangChain callbacks and CrewAI decorators means I can add governance to existing production agents in a day. The sub-millisecond latency means there's no excuse not to ship it. This is the security baseline for any team deploying autonomous agents.”
“This is well-packaged prompt engineering, not a fundamentally new capability. The value depends entirely on the underlying agent following instructions reliably — which varies wildly across tools and models. Teams that haven't established basic code review processes will use this as a crutch rather than building genuine engineering discipline.”
“Microsoft's track record of open-source projects going cold after the initial PR wave is real. Enterprise security buyers will want hardened, commercially supported versions — and AGT's path to that is unclear. Also, a stateless policy engine can't catch all emergent agentic behaviors at runtime.”
“The real innovation here is treating agent behavior as versionable, shareable code. The next step is organizations maintaining their own agent-skills forks as living engineering standards — the CLAUDE.md pattern is becoming a de facto org-level configuration layer for how teams interact with AI.”
“The governance layer is always the last thing built and the first thing regulators demand. Releasing this as MIT open-source before EU AI Act enforcement kicks in is strategically perfect — Microsoft is writing the standard that compliance buyers will require. This becomes table stakes for enterprise agent deployments by 2027.”
“The /spec and /plan commands are genuinely useful for non-engineers who need to communicate feature requirements to an AI agent. Clear structured specs reduce the back-and-forth of vague prompts — this could be the bridge between product thinking and implementation.”
“Honestly, even creative teams need this — I've seen AI agents hallucinate file deletions and unauthorized API calls. Having a policy layer that sandboxes what agents can touch gives me the confidence to actually automate my workflow without fear of a runaway agent trashing production assets.”
Weekly AI Tool Verdicts
Get the next comparison in your inbox
New AI tools ship daily. We compare them before you waste an afternoon.