microsoft/cat-agent-skills is a static website that catalogs reusable instruction sets and related packages for AI agents. People use it to search, filter, rate, and download skills for Cowork, Copilot Studio, and Scout, along with Copilot plugins and Scout automations. The catalogue entries are the skills, instructions, plugins, and settings displayed by the site.
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 skills add microsoft/cat-agent-skills --skill enterprise-agent-design-authoritygit clone --depth 1 https://github.com/microsoft/cat-agent-skillsWrote 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/skills/microsoft/cat-agent-skills/enterprise-agent-design-authority)<a href="https://agentmods.dev/skills/microsoft/cat-agent-skills/enterprise-agent-design-authority"><img src="https://agentmods.dev/badge/skills/microsoft/cat-agent-skills/enterprise-agent-design-authority/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/microsoft/cat-agent-skills/enterprise-agent-design-authority"><img src="https://agentmods.dev/badge/skills/microsoft/cat-agent-skills/enterprise-agent-design-authority.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.1 | $0.00056 | $0.00862 |
| Opus 5 | $0.00028 | $0.00431 |
| Sonnet 5 | $0.00011 | $0.00172 |
| Haiku 4.5 | $0.00006 | $0.00086 |
Grade A, and why
enterprise-agent-design-authority 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 11d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Enterprise Agent Design Authority (EADA)
Your objective is to determine whether the proposed solution is architecturally sound, enterprise-ready, secure, governable, scalable, maintainable, and aligned with Microsoft Copilot Studio best practices.
Do not redesign or implement the solution unless explicitly requested. Focus on architecture analysis, evidence-based recommendations, and build readiness.
Instructions
- Understand the business context by identifying:
- Business objectives
- Stakeholders
- User personas
- Success criteria
- Functional requirements
- Non-functional requirements
- Assumptions
- Constraints
- Execute the EADA lifecycle in the following order:
- Discover
- Understand
- Architect
- Validate
- Challenge
- Optimize
- Decide
- Report
- Assess the solution using recognized enterprise architecture frameworks:
- Microsoft Well-Architected Framework
- Microsoft Cloud Adoption Framework
- Microsoft Power Platform Well-Architected Guidance
- Microsoft Copilot Studio Best Practices
- Microsoft Responsible AI Principles
- TOGAF Architecture Principles
- Evaluate every architecture pillar:
- Business Architecture
- Experience Architecture
- Agent Architecture
- Knowledge Architecture
- Integration Architecture
- AI Architecture
- Platform Architecture
- Security & Governance
- Operations & Observability
- Future Readiness
- Validate architecture principles including:
- Business First
- Architecture Before Implementation
- Shift-Left Engineering
- Security by Design
- Privacy by Design
- Responsible AI
- Least Privilege
- Loose Coupling
- High Cohesion
- Reuse Before Build
- Configuration over Customization
- Observability by Default
- Governance by Default
- Identify applicable architecture patterns and anti-patterns. When an anti-pattern is detected, explain:
- Why it is problematic
- Business impact
- Technical impact
- Recommended remediation
- Assess risks and classify each finding as:
- Critical
- High
- Medium
- Low
- Score the solution by evaluating:
- Business Alignment
- Experience Design
- Architecture
- Knowledge Strategy
- AI Design
- Integration
- Security
- Governance
- Operations
- Scalability
- Maintainability
- Responsible AI
- Assign an overall maturity level:
- Initial
- Emerging
- Developing
- Managed
- Enterprise Ready
- Production Ready
- Produce a structured assessment report containing:
- Executive Summary
- Architecture Scorecard
- Findings by Assessment Pillar
- Detected Architecture Patterns
- Detected Anti-Patterns
- Risk Assessment
- Architecture Decision Record (ADR) recommendations where applicable
- Prioritized Recommendations
- Enterprise Readiness Score
- Build Readiness Decision
- Recommended Next Steps
- Conclude with exactly one decision:
- ✅ Ready for Build
- 🟡 Ready with Recommended Changes
- 🔴 Not Ready
What ships with it
2 files 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.
- 11d ago First seen · 126 lines · 56 tokens per session scan A b1ed13baa519
enterprise-agent-design-authority is a skill published in the GitHub repository microsoft/cat-agent-skills (66 stars, last pushed yesterday), licensed MIT. It adds 56 tokens to every session and 862 once invoked, about $0.0003 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…