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/dojogenesis/mcp/skill-creationnpx skills add DojoGenesis/mcp --skill skill-creationgit clone --depth 1 https://github.com/DojoGenesis/mcpWrote 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/dojogenesis/mcp/skill-creation)<a href="https://agentmods.dev/skills/dojogenesis/mcp/skill-creation"><img src="https://agentmods.dev/badge/skills/dojogenesis/mcp/skill-creation.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.00068 | $0.02279 |
| Opus 5 | $0.00034 | $0.01140 |
| Sonnet 5 | $0.00014 | $0.00456 |
| Haiku 4.5 | $0.00007 | $0.00228 |
Grade A, and why
skill-creation 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 3d 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 — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Creation
I. Philosophy: Skills Encode Thinking, Not Tool Usage
A skill is not a script. It is not a checklist. It is a pattern of thinking -- a way of approaching a class of problems that any competent agent can execute, regardless of what tools are available.
The agent is already smart. It can write code, parse files, search the web, and reason about complex problems. What it lacks is your domain knowledge: the institutional conventions, the hard-won patterns, the "we tried X and it failed because of Y" lessons that took months to learn.
A good skill provides exactly this: the knowledge gap between general intelligence and domain expertise. Nothing more. The context window is a shared resource -- every token in a skill must justify its cost.
Progressive Disclosure
Skills load in three tiers:
- Metadata (~100 words) -- Always in context. The YAML
descriptionfield determines whether the skill activates. - SKILL.md body (<500 lines) -- Loaded when the skill triggers. Contains the core workflow.
- Bundled resources -- Loaded on demand. Templates, references, scripts, examples.
This architecture means: the description field is the most important part of the skill. If the description doesn't capture when to use the skill, the body never loads.
II. When to Use This Skill
- Creating a new skill from scratch for a domain, tool, or workflow
- Updating an existing skill that needs restructuring or enrichment
- Designing skill architecture for a new skills ecosystem
- Formalizing a repeatable workflow that agents should follow consistently
- Capturing domain expertise that would otherwise live only in someone's head
- Reviewing a skill's quality against structural standards
- Onboarding someone to the skill creation process
When NOT to use: If the knowledge is a simple fact or reminder (not a process), it should be a seed, not a skill. If the knowledge is tool-specific and non-transferable, it should be documentation, not a skill.
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.
- 3d ago First seen · 231 lines · 68 tokens per session scan A 95a3eb57d4b2
skill-creation is a skill published in the GitHub repository DojoGenesis/mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 68 tokens to every session and 2,279 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-31.
Other skills, from other repositories
dd-code-generation
Use pup CLI for immediate Datadog operations or generate code for integration into applications.
redux-to-swr
Migrate React components from Redux + Saga to SWR hooks. Use when converting data fetching from Redux store (reducers, sagas, selectors, connect HOC) to SWR-based hooks in CockroachDB DB Console or cluster-ui.
mma-investigator
Expert system for investigating MMA (Multi-Metric Allocator) behavior on CockroachDB clusters. Helps oncall engineers diagnose load imbalances, understand rebalancing decisions, and identify why MMA did or didn't act.
file-crdb-issue
Use when filing, creating, or reporting GitHub issues for CockroachDB. Use when asked to open a bug report, feature request, investigation issue, or performance inquiry. Also use when the user mentions wanting to track a problem, report a regression, or document unexpected behavior in CockroachDB.
engflow-artifacts
Use when downloading test logs, artifacts, or outputs.zip from EngFlow build invocations. Use when investigating CockroachDB CI test failures hosted on mesolite.cluster.engflow.com.
release-discord-post
Create a Discord-ready Neva release announcement from a GitHub release payload. Use for official Neva Discord release posts.