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/c0ntr0lledcha0s/claude-code-plugin-automations/example-skillnpx skills add C0ntr0lledCha0s/claude-code-plugin-automations --skill example-skillgit clone --depth 1 https://github.com/C0ntr0lledCha0s/claude-code-plugin-automationsWrote 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/c0ntr0lledcha0s/claude-code-plugin-automations/example-skill)<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>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.00033 | $0.00533 |
| Opus 5 | $0.00016 | $0.00267 |
| Sonnet 5 | $0.00007 | $0.00107 |
| Haiku 4.5 | $0.00003 | $0.00053 |
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.
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
- Capability 1: Detailed description
- Capability 2: Detailed description
- 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:
- Access Resources: Use
{baseDir}to reference files in this skill directory - Run Scripts: Execute helper scripts from
{baseDir}/scripts/when needed - Reference Docs: Consult
{baseDir}/references/for detailed information - 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:
- Automatically analyze the configuration structure
- Validate against schema using
{baseDir}/scripts/validator.sh - Suggest improvements based on
{baseDir}/references/best-practices.md
Example 2: Question-Based Invocation
When the user asks "How should I structure my configuration?":
- Reference
{baseDir}/references/patterns.md - Provide template from
{baseDir}/assets/template.json - 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
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.
- 5d ago First seen · 73 lines · 33 tokens per session scan A 17fd3403a621
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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…