Borrowing it
Nothing to install: this file belongs to bitovi/cascade-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/bitovi/cascade-mcp/main/.github/skills/create-skill/SKILL.mdgit clone --depth 1 https://github.com/bitovi/cascade-mcpWrote 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/bitovi/cascade-mcp/create-skill)<a href="https://agentmods.dev/skills/bitovi/cascade-mcp/create-skill"><img src="https://agentmods.dev/badge/skills/bitovi/cascade-mcp/create-skill/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/bitovi/cascade-mcp/create-skill"><img src="https://agentmods.dev/badge/skills/bitovi/cascade-mcp/create-skill.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.00053 | $0.01510 |
| Opus 5.5 | $0.00021 | $0.00604 |
| Sonnet 5.5 | $0.00011 | $0.00302 |
| Haiku 4.5 | $0.00005 | $0.00151 |
Grade A, and why
create-skill 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 1mo 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 — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Creating Agent Skills
This skill teaches how to create Agent Skills for this project following the VS Code Agent Skills standard.
What Are Agent Skills?
Agent Skills are folders of instructions, scripts, and resources that AI agents (Copilot, Claude, etc.) can load when relevant to perform specialized tasks. They are:
- Portable: Work across VS Code, Copilot CLI, and GitHub Copilot coding agent
- On-demand: Only loaded when relevant to the current task
- Composable: Multiple skills can work together
- Resource-rich: Can include scripts, examples, templates, and documentation
When to Create a Skill
Create a skill when you need to:
- Document a repeatable workflow or process
- Teach domain-specific knowledge that applies to multiple tasks
- Provide scripts, templates, or examples for common operations
- Define specialized capabilities that go beyond coding standards
Don't create a skill when you just need:
- Coding standards or style guidelines → Use custom instructions instead
- One-time documentation → Use regular markdown files
- File-specific rules → Use glob-based instructions
Skill Directory Structure
.github/skills/
└── your-skill-name/
├── SKILL.md # Required: Skill definition
├── script.sh # Optional: Helper scripts
├── template.ts # Optional: Code templates
└── examples/ # Optional: Example files
└── example-1.md
SKILL.md Format
Every skill must have a SKILL.md file with YAML frontmatter:
---
name: skill-name
description: Clear description of what the skill does and when to use it
---
# Skill Title
Detailed instructions, guidelines, and examples...
Frontmatter Fields
| Field | Required | Description |
|---|---|---|
name |
Yes | Unique identifier, lowercase with hyphens (max 64 chars) |
description |
Yes | What it does and when to use it (max 1024 chars) |
Writing Effective Descriptions
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.
- 1mo ago First seen · 221 lines · 53 tokens per session scan A bbc6aa93f0cb
create-skill is a skill published in the GitHub repository bitovi/cascade-mcp (24 stars, last pushed 2mo ago), licensed MIT. It adds 53 tokens to every session and 1,510 once invoked, about $0.0002 per session on Opus 5.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
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…