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/code-saurabh/openskills/skill-creatornpx skills add CODE-SAURABH/OpenSkills --skill skill-creatorgit clone --depth 1 https://github.com/CODE-SAURABH/OpenSkillsWhat 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.00089 | $0.03156 |
| Opus 5 | $0.00044 | $0.01578 |
| Sonnet 5 | $0.00018 | $0.00631 |
| Haiku 4.5 | $0.00009 | $0.00316 |
Grade A, and why
skill-creator 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 yesterday.
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 — 331 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Creator
A skill is a reusable, opinionated expert guide that makes an AI agent dramatically better at a specific domain. Not a prompt. Not a template. A skill is a production-grade system that encodes deep domain expertise, principled workflows, concrete examples, and an unambiguous definition of done — so the agent executes it the same way every time, without the user having to re-explain.
Your job in this skill is to help the user go from "I want a skill for X" to a skill that works reliably in the real world.
Skill Creator Principles
- Understand before writing. A skill written without understanding the user's intent produces generic instructions that could apply to anything. Ask the right questions first.
- Skills generalize — test cases are just accelerants. You iterate on 3–5 examples because it's fast. But the skill needs to work on the 10,000th prompt that nobody has seen yet. Avoid overfitting rules to the specific examples.
- Explain the why, not just the what. Instructions that say "always do X" without explanation get followed blindly in the wrong context. Instructions that say "do X because Y" get applied with judgment. Smart models respond better to reasoning than to commandments.
- Lean beats padded. Remove every instruction that isn't actively improving outputs. A 600-line skill where 200 lines are filler produces worse results than a tight 300-line skill where every line earns its place. If you find yourself writing ALWAYS/NEVER in all caps, step back — try explaining the reasoning instead.
- The description field is a trigger, not a summary. The description is what the agent reads to decide whether to load the skill. It must contain explicit trigger conditions: "Use when the user asks to..." — not just what the skill is about.
- Test against reality, not intuition. You cannot know if a skill works without running it. Gut-feel improvements compound errors. Run test cases. Look at the outputs. Iterate on evidence.
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.
- yesterday First seen · 331 lines · 89 tokens per session scan A 7a52b58aef21
skill-creator is a skill published in the GitHub repository CODE-SAURABH/OpenSkills (2 stars, last pushed 1mo ago), licensed MIT. It adds 89 tokens to every session and 3,156 once invoked, about $0.0004 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
create-plugin
This skill should be used when the user asks to "create a plugin", "make a GitHub plugin", "turn my repo into a plugin", "create a Claude Code plugin", "create a Codex plugin", "publish my skills as a plugin", or "set up a plugin marketplace". Scaffolds the complete file structure for a repo that works as both a…
adversary
Adversarial pressure-test of a decision, plan, or piece of work. Articulates the case FOR the current approach, then spawns a subagent to steel-man the best alternative, returns a synthesis with mandatory verdict. Invoke ONLY via /adversary — do NOT trigger on 'what do you think' or 'any concerns'.
skill-forge-build
Scaffold and build Claude Code skills from plans or descriptions. Generates SKILL.md files, sub-skills, scripts, references, agents, and templates following the Agent Skills standard. Use when user says "build skill", "scaffold skill", "generate skill", "create SKILL.md", or "implement skill".
skill-portfolio-repo-placement-scan
Scan a portfolio of authored Claude Code skills and produce, per target repo, a precise list of which skills to ADD, which to UPDATE (with direction), and which to CROSS-LINK rather than copy. Uses a per-repo function-level inclusion bar, portfolio deduplication (never recommend a skill already homed as its own repo…
create-skill
Create and validate vault skills. USE WHEN create skill, new skill, skill structure, validate skill, check skill, update skill, add workflow, canonicalize skill, fix skill structure.
create-agent
Create and validate Domain Agents for PAL Second Brain. USE WHEN create agent, new agent, domain agent, validate agent, check agent.