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/kid-sid/codex-spellbook/codex-skill-generatornpx skills add kid-sid/codex-spellbook --skill codex-skill-generatorgit clone --depth 1 https://github.com/kid-sid/codex-spellbookWrote 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/kid-sid/codex-spellbook/codex-skill-generator)<a href="https://agentmods.dev/skills/kid-sid/codex-spellbook/codex-skill-generator"><img src="https://agentmods.dev/badge/skills/kid-sid/codex-spellbook/codex-skill-generator.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.00054 | $0.01025 |
| Opus 5 | $0.00027 | $0.00513 |
| Sonnet 5 | $0.00011 | $0.00205 |
| Haiku 4.5 | $0.00005 | $0.00103 |
Grade A, and why
codex-skill-generator 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Skill Generator
Create focused Codex skills that trigger reliably, stay small, and encode reusable judgment instead of generic prose.
When to Activate
- Create a new skill for this repo
- Refactor a large guidance document into a skill
- Tighten a weak
descriptionso the skill triggers correctly - Convert AGENTS-style guidance into
skills/<name>/SKILL.md - Review an existing skill for format drift
- Add examples, tables, or a checklist to a thin skill
- Update the README inventory after adding a skill
Build Order
| Step | Do |
|---|---|
| 1 | Pick one narrow domain with clear activation triggers |
| 2 | Write a dense description that says what the skill does, when to use it, AND when NOT to use it |
| 3 | Add 6-8 verb-led items under ## When to Activate |
| 4 | Organize the body around decisions, examples, and checklists |
| 5 | End with a shipping-oriented checklist |
| 6 | Update the repo inventory and validation surface |
Required Format
---
name: kebab-case-name
description: Dense sentence that says what the skill does, when to use it, AND when NOT to use it (scope boundary). Codex uses this for implicit activation matching.
---
# Title
One-sentence summary.
## When to Activate
- Verb-led trigger
## Content Sections
## Checklist
- [ ] Shipping check
Rules:
- Folder name must match
name. - Frontmatter must contain only
nameanddescription. - Put activation hints AND scope boundaries in
description; that is what Codex matches against for implicit invocation. - Include at least one decision or comparison table.
- Include at least one
BAD/GOODpair. - Keep the body terse and directly operational.
- Optionally add
agents/openai.yamlto the skill folder to setinterfacemetadata,policy.allow_implicit_invocation, anddependencies.tools(e.g. required MCP servers).
What Good Skills Contain
| Include | Why |
|---|---|
Trigger language in description |
Helps the skill load at the right time |
| Decision tables | Compress tradeoffs without bloating prose |
| Realistic code or command examples | Makes the guidance executable |
| A checklist | Gives Codex a final pass before finishing |
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 · 142 lines · 54 tokens per session scan A 741745236591
codex-skill-generator is a skill published in the GitHub repository kid-sid/codex-spellbook (21 stars, last pushed 3mo ago), licensed MIT. It adds 54 tokens to every session and 1,025 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…