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/cyperx84/claude-code-plugin-examples/snippet-generatornpx skills add cyperx84/claude-code-plugin-examples --skill snippet-generatorgit clone --depth 1 https://github.com/cyperx84/claude-code-plugin-examplesWrote 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/cyperx84/claude-code-plugin-examples/snippet-generator)<a href="https://agentmods.dev/skills/cyperx84/claude-code-plugin-examples/snippet-generator"><img src="https://agentmods.dev/badge/skills/cyperx84/claude-code-plugin-examples/snippet-generator.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.00020 | $0.03026 |
| Opus 5 | $0.00010 | $0.01513 |
| Sonnet 5 | $0.00004 | $0.00605 |
| Haiku 4.5 | $0.00002 | $0.00303 |
Grade A, and why
Snippet Generator 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 — 549 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Snippet Generator
Purpose
Create production-ready code snippets that:
- Follow language best practices
- Are properly documented
- Include error handling
- Are customizable with parameters
- Save development time
When to Use
Invoke this skill when:
- User needs boilerplate code quickly
- Creating common patterns (loops, classes, functions)
- Scaffolding new components or modules
- Teaching programming patterns
- Standardizing code across a team
Instructions
Step 1: Identify the Snippet Type
Determine what kind of snippet is needed:
- Language construct: Class, function, loop, conditional
- Design pattern: Singleton, factory, observer, etc.
- Framework-specific: React component, Express route, etc.
- Utility: Common algorithm, data structure, helper
- Test pattern: Test suite, test case, mock
Step 2: Determine the Language/Framework
Identify the target environment:
- Language: JavaScript, TypeScript, Python, Go, Rust, Java, etc.
- Framework: React, Vue, Express, Django, Spring, etc.
- Version: ES6+, TypeScript 5+, Python 3.10+, etc.
Step 3: Apply Best Practices
Ensure the snippet includes:
- Type safety: Types/interfaces where applicable
- Error handling: Try/catch, error checking
- Documentation: JSDoc, docstrings, comments
- Naming: Clear, descriptive names
- Modern syntax: Latest language features
- Testing: Testable structure
Step 4: Add Customization Placeholders
Include placeholders for:
- Names:
${ComponentName},${functionName} - Parameters:
${param1},${options} - Types:
${Type},${ReturnType} - Values:
${defaultValue},${initialState}
Step 5: Include Usage Examples
Provide:
- Basic usage example
- Advanced usage (if applicable)
- Common variations
- Integration examples
Snippet Templates
JavaScript/TypeScript
Async Function with Error Handling
/**
* ${description}
* @param ${param} - ${paramDescription}
* @returns ${returnDescription}
* @throws ${errorDescription}
*/
async function ${functionName}(${param}: ${ParamType}): Promise<${ReturnType}> {
try {
// Validate input
if (!${param}) {
throw new Error('${param} is required');
}
// Main logic
const result = await ${operation}(${param});
return result;
} catch (error) {
console.error(`Error in ${functionName}:`, error);
throw new Error(`Failed to ${operation}: ${error.message}`);
}
}
// Usage example
try {
const result = await ${functionName}(${exampleParam});
console.log('Success:', result);
} catch (error) {
console.error('Error:', error);
}
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 · 549 lines · 20 tokens per session scan A 6d948f9d05ab
Snippet Generator is a skill published in the GitHub repository cyperx84/claude-code-plugin-examples (2 stars, last pushed 10mo ago), licensed MIT. It adds 20 tokens to every session and 3,026 once invoked, about $0.0001 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.
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.
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.
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.
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…