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 skills/pnp/copilot-prompts/create-skill-samplenpx skills add pnp/copilot-prompts --skill create-skill-samplegit clone --depth 1 https://github.com/pnp/copilot-promptsWrote 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/pnp/copilot-prompts/create-skill-sample)<a href="https://agentmods.dev/skills/pnp/copilot-prompts/create-skill-sample"><img src="https://agentmods.dev/badge/skills/pnp/copilot-prompts/create-skill-sample.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.00102 | $0.03063 |
| Opus 5 | $0.00051 | $0.01532 |
| Sonnet 5 | $0.00020 | $0.00613 |
| Haiku 4.5 | $0.00010 | $0.00306 |
Grade A, and why
create-skill-sample 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 — 308 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create a New GitHub Copilot Skill Sample
This skill guides creating new custom skill samples for the pnp/copilot-prompts repository. These samples live inside samples/skills/ and represent reusable instruction files (SKILL.md) that teach GitHub Copilot how to perform specific, repeatable tasks.
Before Starting
Critical: Always ask the user for the following information before scaffolding:
- Skill name — a short, descriptive name for the skill (e.g., "Code Review for C#", "API Documentation Generator", "Unit Test Scaffolder")
- Skill purpose — a clear description of what the skill does. What task does it teach GitHub Copilot to perform?
- Trigger phrases — 3–5 example phrases a user might say to activate the skill (e.g., "review my C# code", "generate API docs")
- Inputs needed — what information the skill needs from the user before it can proceed (e.g., a source file, a framework version, a language)
- Output format — what the skill produces (e.g., a Markdown report, generated code files, a checklist)
- Steps — the high-level steps the skill follows (3–7 steps). Each step should be a discrete action.
- Rules — any hard constraints the skill must always follow (e.g., "never modify source files directly")
- Author name — the contributor's full name
- Author GitHub username — the contributor's GitHub handle
If the user doesn't provide all details upfront, ask for the missing ones before proceeding.
Sample Directory Structure
Create the sample in samples/skills/{skill-name}/:
samples/skills/{skill-name}/
├── SKILL.md # The skill definition file (core contribution)
├── README.md # Documentation and usage instructions
├── assets/
│ └── sample.json # Metadata for the M365 Solution Gallery
Folder naming rules:
- Use lowercase and hyphens only (e.g.,
code-review-csharp,api-docs-generator,unit-test-scaffolder) - Do NOT use periods/dots in the folder name
- Keep it concise but descriptive — 2–5 words
- Do NOT include prefixes like
m365-orgithub-— skill folders use plain descriptive names
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 · 308 lines · 102 tokens per session scan A 964e4290ef80
create-skill-sample is a skill published in the GitHub repository pnp/copilot-prompts (859 stars, last pushed 10d ago), licensed MIT. It adds 102 tokens to every session and 3,063 once invoked, about $0.0005 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
create-canvas-extension
Create or register a canvas extension in the awesome-copilot repository. Use when asked to scaffold a new canvas extension, create its plugin.json, add a reusable extension to one or more plugins, or migrate extension metadata. Extensions are reusable source under extensions/; shippable plugin manifests belong under…
apm-review-panel
Use this skill to run a multi-persona expert advisory review on a labelled pull request in microsoft/apm. The panel fans out to five mandatory specialists plus a test-coverage specialist (active on every PR that touches src/) plus three conditional specialists (auth, doc-writer, performance-expert), all running in…
apm-issue-autopilot
Use this skill to drive any open microsoft/apm issue (bug, feature, docs, refactor, perf) from raw intake to a mergeable PR with triage as the central, paramount gate. Run the apm-triage-panel rubric per issue first, then present ONE consolidated triage review for the whole batch and escalate to the maintainer BY…
apm-triage-panel
Use this skill to triage one microsoft/apm issue selected by the daily sweep, the status/needs-triage fast path, or manual dispatch. Emit one synthesized comment with a decision, label set, exact milestone, and suggested next action.
cli-logging-ux
Use this skill when editing or creating CLI output, logging, warnings, error messages, progress indicators, or diagnostic summaries in the APM codebase. Activate whenever code touches console helpers (richsuccess, richwarning, richerror, richinfo, richecho), DiagnosticCollector, STATUSSYMBOLS, CommandLogger, or any…
cut-release
Use this skill to cut an APM release from the current worktree: assess whether the cycle since the last tag warrants a patch or minor bump (semver discipline against the merged-since-last-tag diff), sanitize the [Unreleased] CHANGELOG block into a dated version block with one concise "so what" entry per merged PR…