Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Copilot Surface Audit

ASecurity

Audit a developer's GitHub Copilot configuration across all surfaces (completions, chat IDE, coding agent, cloud agent, mobile) to identify model gaps, plan mismatches, and org-policy constraints. Reach for this skill before recommending a Copilot model — surface and plan scope the answer, not just the model name.

7 stars
0 votes
0 copies
0 views
Added 9/23/2026
ai-agentsgogitsecurity

Security Analysis

A100/100

Scanned 9/23/2026

$npx -y skills add mcorbett51090/RavenClaude --skill copilot-surface-audit --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Copilot Surface Audit?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Copilot Surface Audit
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/mcorbett51090-copilot-surface-audit/badge)](https://www.skillsdirectory.com/skills/mcorbett51090-copilot-surface-audit)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: copilot-surface-audit
description: "Audit a developer's GitHub Copilot configuration across all surfaces (completions, chat IDE, coding agent, cloud agent, mobile) to identify model gaps, plan mismatches, and org-policy constraints. Reach for this skill before recommending a Copilot model — surface and plan scope the answer, not just the model name."
---

# Skill: Copilot Surface Audit

A Copilot model recommendation is only as good as its surface scope. "Model X is available in Copilot" is an incomplete claim until the surface (completions vs. chat vs. coding agent vs. cloud agent vs. mobile) and the plan (Free/Pro/Business/Enterprise) are both confirmed. This skill ensures every recommendation is surface-scoped and plan-gated.

## Step 1 — Identify the active surface(s)

Ask or infer from context which Copilot surface(s) the developer actually uses:

| Surface | Entry point | Model picker location |
|---|---|---|
| Completions | IDE inline ghost-text | No picker — org policy or default applies |
| Chat IDE | IDE sidebar / slash commands | Model picker in chat header |
| Coding agent | IDE-initiated autonomous run | Separate agent surface — plan-gated |
| Cloud agent | GitHub.com / Copilot Workspace | Separate cloud picker — may differ from IDE |
| Mobile | GitHub Mobile app | Mobile-specific subset — narrowest picker |

**Do not conflate surfaces.** A model available in chat IDE may not be available for the coding agent; cloud agent has its own availability list.

## Step 2 — Confirm plan tier

| Plan | Key capabilities | Notes |
|---|---|---|
| Free | Subset of models; monthly usage cap | Narrowest model picker |
| Pro | Full IDE model picker; no monthly cap | Baseline for professional use |
| Business | Org policy controls; team seat management | Adds model rules + audit log |
| Enterprise | Full controls; org model allow/deny list; GHEC required | Broadest governance surface |

> If the developer is on Business or Enterprise, check whether an org admin has applied a **model rules** policy before recommending a specific SKU. See [`../../agents/copilot-model-strategist.md`](../../agents/copilot-model-strategist.md).

## Step 3 — Cross-reference the verified lineup

For each surface × plan combination, confirm model availability in [`../../knowledge/cross-tool-model-lineup-2026.md`](../../knowledge/cross-tool-model-lineup-2026.md) under the Copilot section. Apply the **closed-world rule**: if a model is not in the verified lineup for that surface, do not confirm availability — offer to research.

```
For each candidate model:
  1. Is it in the verified Copilot lineup entry?    → if no: closed-world, do not confirm
  2. Is the plan gate met?                           → if no: explain the plan requirement
  3. Is the surface listed?                          → if no: check mobile/cloud-agent sub-lists
  4. Is there an org model rule that blocks it?      → if yes: escalate to security-reviewer
```

## Step 4 — Summarize the audit result

Produce a surface-scoped summary table:

| Surface | Plan required | Model available? | Gate | Verified date |
|---|---|---|---|---|
| Completions | Pro+ | [verify-at-use] | Plan gate | [retrieval date] |
| Chat IDE | Pro+ | [verify-at-use] | Plan gate | [retrieval date] |
| Coding agent | Business/Enterprise | [verify-at-use] | Surface + plan | [retrieval date] |

Always include the retrieval date and a `[verify-at-use]` marker on any availability claim — Copilot picker contents change weekly.

## Pitfalls

- Confirming model availability without specifying the surface: "X is in Copilot" is never a complete answer.
- Ignoring plan gates on Free-tier users — the Free sub-list is narrower than the full picker.
- Assuming coding-agent and cloud-agent availability matches the IDE chat picker.
- Forgetting to check org model rules for Business/Enterprise org members.
- Quoting the Copilot picker without a retrieval date — it changes without deprecation notice.

## See also

- [`../../agents/copilot-model-strategist.md`](../../agents/copilot-model-strategist.md) — the agent this skill supports
- [`../../knowledge/ai-coding-decision-trees.md`](../../knowledge/ai-coding-decision-trees.md) — the Copilot surface/plan decision tree
- [`../../knowledge/cross-tool-model-lineup-2026.md`](../../knowledge/cross-tool-model-lineup-2026.md) — the dated Copilot lineup

Attribution

mcorbett51090mcorbett51090
View sourceSee grades on GitHubMore from mcorbett51090 →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698431 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →