example-skill

example-skill is a skill for Claude Code, Codex from C0ntr0lledCha0s/claude-code-plugin-automations. It costs 33 tokens per session (533 once invoked), scanned A, original, MIT.

Guidance for creating automatically activated Claude Code skills, which provide context-aware help when relevant tasks, files, questions, or situations are detected.

In plain words
What is it for?
Use it to define automatic assistance for a task, including helper scripts, reference material, reusable templates, and activation conditions.
Why use it?
It explains when the skill should activate and how to use its scripts, reference documents, and templates.

Skill for Claude CodeCodex

Part of the my-full-plugin plugin — 1 skill 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/c0ntr0lledcha0s/claude-code-plugin-automations/example-skill
Any agent
npx skills add C0ntr0lledCha0s/claude-code-plugin-automations --skill example-skill
Clone the repo
git clone --depth 1 https://github.com/C0ntr0lledCha0s/claude-code-plugin-automations

Made for: Claude Code, Codex.

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

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/c0ntr0lledcha0s/claude-code-plugin-automations/example-skill.svg)](https://agentmods.dev/skills/c0ntr0lledcha0s/claude-code-plugin-automations/example-skill)
Your own site
<a href="https://agentmods.dev/skills/c0ntr0lledcha0s/claude-code-plugin-automations/example-skill"><img src="https://agentmods.dev/badge/skills/c0ntr0lledcha0s/claude-code-plugin-automations/example-skill.svg" alt="Measured on agentmods" height="20"></a>
Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 533 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.00033 $0.00533
Opus 5 $0.00016 $0.00267
Sonnet 5 $0.00007 $0.00107
Haiku 4.5 $0.00003 $0.00053

Measured 5d ago against content hash 17fd3403a621, 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 5d 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.

claude-component-builder/skills/building-plugins/templates/full-plugin-template/skills/example-skill/SKILL.md · 73 lines

How it starts

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

Example Skill

You are an expert at performing task X. This skill provides always-on expertise that activates automatically when relevant.

Your Capabilities

  1. Capability 1: Detailed description
  2. Capability 2: Detailed description
  3. Capability 3: Detailed description

When to Use This Skill

Claude should automatically invoke this skill when:

  • The user wants to perform task X
  • Files matching pattern Y are being modified
  • The user asks questions about domain Z
  • Situation W is detected in the codebase

How to Use This Skill

When this skill is activated:

  1. Access Resources: Use {baseDir} to reference files in this skill directory
  2. Run Scripts: Execute helper scripts from {baseDir}/scripts/ when needed
  3. Reference Docs: Consult {baseDir}/references/ for detailed information
  4. Use Templates: Load templates from {baseDir}/assets/ as needed

Resources Available

Scripts

  • {baseDir}/scripts/analyzer.py: Analyzes files for patterns
  • {baseDir}/scripts/validator.sh: Validates syntax and structure

References

  • {baseDir}/references/best-practices.md: Best practices guide
  • {baseDir}/references/patterns.md: Common patterns and anti-patterns

Assets

  • {baseDir}/assets/template.json: Template for generating files

Examples

Example 1: Automatic Invocation on File Type

When the user opens or modifies a .config file:

  1. Automatically analyze the configuration structure
  2. Validate against schema using {baseDir}/scripts/validator.sh
  3. Suggest improvements based on {baseDir}/references/best-practices.md

Example 2: Question-Based Invocation

When the user asks "How should I structure my configuration?":

  1. Reference {baseDir}/references/patterns.md
  2. Provide template from {baseDir}/assets/template.json
  3. Explain best practices with examples

Important Notes

  • This skill auto-invokes based on context
  • Always validate inputs when using scripts
  • Provide clear, actionable guidance
  • Reference documentation for complex scenarios

Read the full file on GitHub · 73 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. 5d ago First seen · 73 lines · 33 tokens per session scan A 17fd3403a621

Subscribe to this mod's changes

example-skill is a skill published in the GitHub repository C0ntr0lledCha0s/claude-code-plugin-automations (3 stars, last pushed 6mo ago), licensed MIT. It adds 33 tokens to every session and 533 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-31.

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

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 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

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…

vercel/next.js · 83 tokens