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/lukerenton/explore-claude-code/build-skillnpx skills add LukeRenton/explore-claude-code --skill build-skillgit clone --depth 1 https://github.com/LukeRenton/explore-claude-codeWrote 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/lukerenton/explore-claude-code/build-skill)<a href="https://agentmods.dev/skills/lukerenton/explore-claude-code/build-skill"><img src="https://agentmods.dev/badge/skills/lukerenton/explore-claude-code/build-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.00051 | $0.01230 |
| Opus 5 | $0.00026 | $0.00615 |
| Sonnet 5 | $0.00010 | $0.00246 |
| Haiku 4.5 | $0.00005 | $0.00123 |
Grade A, and why
build-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.
How it starts
The opening of the file, as written. The whole thing — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a skill builder. You create well-structured, consistent Claude Code SKILL.md files that follow established standards. Your output is a complete, ready-to-use skill file.
Process
1. Assess Input Completeness
Read what the user provided in $ARGUMENTS and the surrounding conversation context. Determine how much is already specified vs what needs clarification.
Categorize as:
- Minimal (just a name or vague idea): Full Q&A needed
- Medium (clear purpose but missing details): Targeted questions only
- Rich (detailed description with specifics): Confirm and clarify 1-2 things
2. Adaptive Q&A
Ask only what's missing. Never re-ask what's already clear. Cover these areas as needed:
- Intent: What problem does this skill solve? What's the trigger scenario?
- Invocation: User-only (
disable-model-invocation: true), Claude-only (user-invocable: false), or both (default)? - Arguments: Does it accept arguments? What format?
- Supporting files: Does it need templates, scripts, or reference docs?
- Team membership: Is this a standalone utility or joining the core agent team?
- Scope: If the skill needs restricted tools, forked execution, or a specific model, suggest building it as an agent instead (skills do not support
allowed-tools,model,context, orhooksfrontmatter).
3. Check for Overlap
Before drafting, scan .claude/skills/ for existing skills with similar purpose. If significant overlap exists, warn the user and suggest modifying the existing skill instead. Proceed only if the user confirms they want a new one.
4. Draft the Skill
Write the SKILL.md following these structural principles:
Supported frontmatter fields (in order):
name
description
argument-hint
disable-model-invocation
user-invocable
These are the ONLY supported skill frontmatter fields: name, description, argument-hint, disable-model-invocation, user-invocable, compatibility, license, metadata. Fields like allowed-tools, model, context, agent, and hooks are NOT supported in skills despite appearing in some documentation. Do not use them.
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 · 114 lines · 51 tokens per session scan A a4056ed96e74
build-skill is a skill published in the GitHub repository LukeRenton/explore-claude-code (308 stars, last pushed 22d ago), licensed MIT. It adds 51 tokens to every session and 1,230 once invoked, about $0.0003 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.
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…