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/metraton/gaia/skill-creationnpx skills add metraton/gaia --skill skill-creationgit clone --depth 1 https://github.com/metraton/gaiaWrote 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/metraton/gaia/skill-creation)<a href="https://agentmods.dev/skills/metraton/gaia/skill-creation"><img src="https://agentmods.dev/badge/skills/metraton/gaia/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.1 | $0.00029 | $0.02991 |
| Opus 5 | $0.00015 | $0.01496 |
| Sonnet 5 | $0.00006 | $0.00598 |
| Haiku 4.5 | $0.00003 | $0.00299 |
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 6d 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Creation
What is a skill?
Injected procedural knowledge -- the "how" for agents. The agent brings identity and domain knowledge. The skill brings process and protocol. They never duplicate each other.
Step 1: Choose the type
Type determines structure. Choose before writing anything.
| Type | Purpose | When it applies |
|---|---|---|
| Discipline | Enforces rules the agent will rationalize around under pressure | command-execution, execution |
| Technique | How to think about or approach a class of problem | investigation, approval |
| Reference | Lookup tables, classifications, format specifications | security-tiers, fast-queries, git-conventions |
| Domain | Project-specific patterns for a technical area | gaia-patterns |
| Protocol | System operating contract -- state machines, mandatory formats | agent-protocol |
Step 1.5: Situate the skill in its flow
With the type chosen, place the skill before you structure it: where it lives in a flow, and what it can affect. Treat these as one gate with two coupled facets -- position is what sets blast radius.
- Position. Is the skill standalone (a self-contained process run from a clean start), or does it run mid-flow -- sometimes after many skills have already executed -- with an upstream that hands it state and a downstream that consumes what it emits?
- Blast radius. What does the skill's output touch or trigger? A standalone technique's reach ends at its own result; a mid-flow skill's is amplified, because its output becomes the next step's input.
The consequence is why the gate exists. A mid-flow skill inherits state and assumptions from upstream; write it as though it started clean and it either redoes work already settled or emits what the next step cannot consume -- and because that output is consumed downstream, the break propagates instead of staying local. A wrong position mis-scopes everything the skill's process assumes and produces.
What ships with it
2 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.
- 6d ago First seen · 129 lines · 29 tokens per session scan A 80c6b2125840
skill-creation is a skill published in the GitHub repository metraton/gaia (3 stars, last pushed yesterday), licensed MIT. It adds 29 tokens to every session and 2,991 once invoked, about $0.0001 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
review-team
6つの専門レビュアーロールを並列実行し、consensusLevel（複数ロールの合意度）と Tech Lead レポート（top3指摘・blindSpots・consensusSummary）で結果を統合する マルチエージェントレビュー entry skill。 Parallel multi-role review with consensus scoring (consensusLevel) and Tech Lead report. Use when a major release needs exhaustive multi-angle review, or when a single-perspective review…
ultra
Fans the work out as a fleet of parallel Grok and Codex agents billed to their own subscriptions, then synthesizes one result. The peer engine equivalent of ultracode, adding intensity without spending Claude quota on the fleet. Use it for genuinely broad goals, not only explicit asks for intensity.
grok-prompting
Brief writing guidance for composing self contained Grok briefs for coding, review, diagnosis, and second opinion tasks.
smoke
Runs a three probe live smoke wave after a plugin update and reports gate chain health before real work rides it.
codex-result-handling
Internal contract for returning Codex companion output without alteration.
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - reproduce and isolate before changing anything.