example-skill

example-skill is a skill for Claude Code, Codex from xiaoyuge886/aigc. It costs 48 tokens per session (565 once invoked), scanned A, original, MIT.

A reference example showing how to structure a Claude Code plugin skill, a set of instructions that an AI assistant uses when a task matches its purpose. It documents trigger conditions, required files, optional resources, and metadata.

In plain words
What is it for?
Demonstrating skills, creating skill templates, explaining plugin-skill structure, and learning common patterns for skill development.
Why use it?
It gives skill authors a concrete pattern to follow instead of designing the folder structure and instructions from scratch.

Skill for Claude CodeCodex

Part of the example-plugin plugin — 1 skill, 1 command shipped together

Install

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.

agentmods
npx agentmods add skills/xiaoyuge886/aigc/example-skill
Any agent
npx skills add xiaoyuge886/aigc --skill example-skill
Clone the repo
git clone --depth 1 https://github.com/xiaoyuge886/aigc

Made for: Claude Code, Codex.

Or install example-plugin, the plugin that ships this one along with the rest of its 1 skill, 1 command.

Wrote 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.

agentmods badge for example-skill

README.md
[![agentmods](https://agentmods.dev/badge/skills/xiaoyuge886/aigc/example-skill.svg)](https://agentmods.dev/skills/xiaoyuge886/aigc/example-skill)
Your own site
<a href="https://agentmods.dev/skills/xiaoyuge886/aigc/example-skill"><img src="https://agentmods.dev/badge/skills/xiaoyuge886/aigc/example-skill.svg" alt="Measured on agentmods" height="20"></a>
Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 565 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00048 $0.00565
Opus 5 $0.00024 $0.00282
Sonnet 5 $0.00010 $0.00113
Haiku 4.5 $0.00005 $0.00056

Measured 4d ago against content hash 87d90442621a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

example-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 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.

Origin

Copies of this mod

5 near-identical copies found in the catalogue:

plugins/claude-plugins-official-main/plugins/example-plugin/skills/example-skill/SKILL.md · 85 lines

How it starts

The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Example Skill

This skill demonstrates the structure and format for Claude Code plugin skills.

Overview

Skills are model-invoked capabilities that Claude autonomously uses based on task context. Unlike commands (user-invoked) or agents (spawned by Claude), skills provide contextual guidance that Claude incorporates into its responses.

When This Skill Applies

This skill activates when the user's request involves:

  • Creating or understanding plugin skills
  • Skill template or reference needs
  • Skill development patterns

Skill Structure

Required Files

skills/
└── skill-name/
    └── SKILL.md          # Main skill definition (required)

Optional Supporting Files

skills/
└── skill-name/
    ├── SKILL.md          # Main skill definition
    ├── README.md         # Additional documentation
    ├── references/       # Reference materials
    │   └── patterns.md
    ├── examples/         # Example files
    │   └── sample.md
    └── scripts/          # Helper scripts
        └── helper.sh

Frontmatter Options

Skills support these frontmatter fields:

  • name (required): Skill identifier
  • description (required): Trigger conditions - describe when Claude should use this skill
  • version (optional): Semantic version number
  • license (optional): License information or reference

Writing Effective Descriptions

The description field is crucial - it tells Claude when to invoke the skill.

Good description patterns:

description: This skill should be used when the user asks to "specific phrase", "another phrase", mentions "keyword", or discusses topic-area.

Include:

  • Specific trigger phrases users might say
  • Keywords that indicate relevance
  • Topic areas the skill covers

Skill Content Guidelines

  1. Clear purpose: State what the skill helps with
  2. When to use: Define activation conditions
  3. Structured guidance: Organize information logically
  4. Actionable instructions: Provide concrete steps
  5. Examples: Include practical examples when helpful

Read the full file on GitHub · 85 lines

Changes

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.

  1. 4d ago First seen · 85 lines · 48 tokens per session scan A 87d90442621a

Subscribe to this mod's changes

example-skill is a skill published in the GitHub repository xiaoyuge886/aigc (197 stars, last pushed 1mo ago), licensed MIT. It adds 48 tokens to every session and 565 once invoked, about $0.0002 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens