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 skills add nodnarbnitram/claude-code-extensions --skill skill-skeletongit clone --depth 1 https://github.com/nodnarbnitram/claude-code-extensionsWrote 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 [object Object]](/badge/skills/nodnarbnitram/claude-code-extensions/skill-skeleton/github.svg?v=0-8-A){kind=icon}
[](https://agentmods.dev/skills/nodnarbnitram/claude-code-extensions/skill-skeleton)<a href="https://agentmods.dev/skills/nodnarbnitram/claude-code-extensions/skill-skeleton"><img src="https://agentmods.dev/badge/skills/nodnarbnitram/claude-code-extensions/skill-skeleton/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
![agentmods 80×15 button for [object Object]](/badge/skills/nodnarbnitram/claude-code-extensions/skill-skeleton.svg?v=A-x){kind=icon}
<a href="https://agentmods.dev/skills/nodnarbnitram/claude-code-extensions/skill-skeleton"><img src="https://agentmods.dev/badge/skills/nodnarbnitram/claude-code-extensions/skill-skeleton.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00008 | $0.00963 |
| Opus 5.5 | $0.00003 | $0.00385 |
| Sonnet 5.5 | $0.00002 | $0.00193 |
| Haiku 4.5 | $0.00001 | $0.00096 |
Grade A, and why
[object Object] 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 1mo 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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{{SKILL_TITLE}}
{{ONE_LINE_DESCRIPTION}}
⚠️ BEFORE YOU START
This skill prevents {{ERROR_COUNT}} common errors and saves ~{{TOKEN_SAVINGS}}% tokens.
| Metric | Without Skill | With Skill |
|---|---|---|
| Setup Time | {{MANUAL_TIME}} | {{SKILL_TIME}} |
| Common Errors | {{ERROR_COUNT}} | 0 |
| Token Usage | {{MANUAL_TOKENS}} | {{SKILL_TOKENS}} |
Known Issues This Skill Prevents
- {{PREVENTED_ISSUE_1}}
- {{PREVENTED_ISSUE_2}}
- {{PREVENTED_ISSUE_3}}
Quick Start
Step 1: {{FIRST_STEP_TITLE}}
{{FIRST_STEP_CODE}}
Why this matters: {{FIRST_STEP_EXPLANATION}}
Step 2: {{SECOND_STEP_TITLE}}
{{SECOND_STEP_CODE}}
Why this matters: {{SECOND_STEP_EXPLANATION}}
Step 3: {{THIRD_STEP_TITLE}}
{{THIRD_STEP_CODE}}
Why this matters: {{THIRD_STEP_EXPLANATION}}
Critical Rules
✅ Always Do
- ✅ {{DO_1}}
- ✅ {{DO_2}}
- ✅ {{DO_3}}
❌ Never Do
- ❌ {{DONT_1}}
- ❌ {{DONT_2}}
- ❌ {{DONT_3}}
Common Mistakes
❌ Wrong:
{{WRONG_CODE}}
✅ Correct:
{{CORRECT_CODE}}
Why: {{EXPLANATION}}
Known Issues Prevention
| Issue | Root Cause | Solution |
|---|---|---|
| {{ISSUE_1}} | {{CAUSE_1}} | {{SOLUTION_1}} |
| {{ISSUE_2}} | {{CAUSE_2}} | {{SOLUTION_2}} |
| {{ISSUE_3}} | {{CAUSE_3}} | {{SOLUTION_3}} |
Configuration Reference
{{CONFIG_FILE_NAME}}
{{CONFIG_EXAMPLE}}
Key settings:
{{SETTING_1}}: {{SETTING_1_DESCRIPTION}}{{SETTING_2}}: {{SETTING_2_DESCRIPTION}}
Common Patterns
{{PATTERN_1_NAME}}
{{PATTERN_1_CODE}}
{{PATTERN_2_NAME}}
{{PATTERN_2_CODE}}
Bundled Resources
Scripts
Located in scripts/:
{{SCRIPT_1}}- {{SCRIPT_1_DESCRIPTION}}
References
Located in references/:
{{REFERENCE_1}}- {{REFERENCE_1_DESCRIPTION}}{{REFERENCE_2}}- {{REFERENCE_2_DESCRIPTION}}
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 184 lines · 8 tokens per session scan A c944e79d4907
[object Object] is a skill published in the GitHub repository nodnarbnitram/claude-code-extensions (16 stars, last pushed 6mo ago), licensed MIT. It adds 8 tokens to every session and 963 once invoked, about $0.0000 per session on Opus 5.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-09-03.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…