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 commands/nodnarbnitram/claude-code-extensions/create-skillgit clone --depth 1 https://github.com/nodnarbnitram/claude-code-extensionsWhat 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.00009 | $0.01525 |
| Opus 5 | $0.00005 | $0.00763 |
| Sonnet 5 | $0.00002 | $0.00305 |
| Haiku 4.5 | $0.00001 | $0.00153 |
Grade A, and why
create-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 2d 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create New Skill
You will create a new skill for Claude Code based on the provided name, description, and optional documentation URLs.
Arguments: $ARGUMENTS
Important:
- First argument: skill name (kebab-case)
- Second argument: description/purpose (in quotes)
- Remaining arguments (optional): documentation URLs to analyze
Your Task
Follow these steps to create the skill:
Step 1: Parse Arguments
Extract from $ARGUMENTS:
- Skill Name: The first argument (kebab-case identifier, e.g.,
pdf-processor) - Description/Purpose: The second argument (in quotes) describing what the skill does
- Documentation URLs: Any remaining arguments (optional)
Examples:
/create-skill pdf-processor "Extract text and tables from PDF files"/create-skill temporal-workflow "Build durable workflows" https://docs.temporal.io https://typescript.temporal.io
Step 2: Gather Context
If documentation URLs were provided: Launch technical-researcher agents in parallel (one per URL) to analyze the documentation. Each researcher should investigate:
- Key concepts, APIs, and patterns relevant to the skill's purpose
- Best practices and conventions
- Common workflows and use cases
- Important implementation details
- Configuration examples and templates that should be bundled
IMPORTANT: Do NOT use WebFetch directly. Always use the technical-researcher agent to ensure comprehensive analysis and proper extraction of reusable content.
If NO documentation URLs were provided: Use the AskUserQuestion tool to gather more information. Ask about:
- What specific problem does this skill solve?
- Are there documentation URLs or references to analyze?
- What tools will the skill need access to? (Read-only? Bash access?)
- What are the key workflows and steps?
- What trigger keywords should activate this skill?
Adapt questions based on the description provided - skip questions that are already answered.
Step 3: Copy Skeleton Template
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.
- 2d ago First seen · 181 lines · 9 tokens per session scan A 03a3c9cd8fbe
create-skill is a command published in the GitHub repository nodnarbnitram/claude-code-extensions (16 stars, last pushed 4mo ago), licensed MIT. It adds 9 tokens to every session and 1,525 once invoked, about $0.0000 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.