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 skills add Zts0hg/codexspec --skill codexspec-spec-to-plangit clone --depth 1 https://github.com/Zts0hg/codexspecWrote 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/zts0hg/codexspec/codexspec-spec-to-plan)<a href="https://agentmods.dev/skills/zts0hg/codexspec/codexspec-spec-to-plan"><img src="https://agentmods.dev/badge/skills/zts0hg/codexspec/codexspec-spec-to-plan.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.00022 | $0.01421 |
| Opus 5 | $0.00011 | $0.00711 |
| Sonnet 5 | $0.00004 | $0.00284 |
| Haiku 4.5 | $0.00002 | $0.00142 |
Grade A, and why
codexspec:spec-to-plan 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Specification to Plan Converter
Language Preference
Read .codexspec/config.yml. Two independent language controls apply (each falls back to language.output, then English):
- Interaction language (
language.interaction): language for all conversation with the user — questions, explanations, status messages, andcodexspecCLI terminal output. - Document language (
language.document): language for generated artifact files (requirements/spec/plan/tasks).
Converse in the interaction language and author artifacts in the document language. Apply the project's translation standard to both: translate by meaning (not word-for-word), keep English for terms with no good native equivalent, and write as if originally in that language.
User Input
the text after the $codexspec:spec-to-plan skill mention
Role
Act as an implementation planner. Define how to build the confirmed design in phases while preserving confirmed user intent. The design (design.md) already defines what the system is — architecture, components, interfaces, and key design decisions. Do not redo that design here: consume it and plan how to implement it (phases, ordering, verification).
Feature Resolution
Use an explicit path first, then the current branch. If neither uniquely identifies a feature, ask the user to select one. Never silently select the latest feature.
Read:
requirements.mdspec.mddesign.md.codexspec/memory/constitution.mdwhen present- Relevant repository files needed to verify existing patterns and constraints
Design-stage compatibility: if design.md is absent (a legacy feature created before the design stage), plan directly from spec.md and state that no separate design artifact was available.
Legacy compatibility: if requirements.md is absent, treat spec.md as the temporary highest authority and disclose that original-discussion fidelity cannot be checked.
Authority and Stop Conditions
Authority order:
- Confirmed
requirements.md spec.md- Constitution and verified repository facts
design.md- Plan-level technical decisions
- General best practices
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 Changed · +7 lines 9e6a4045daad
- 7d ago First seen · 118 lines · 22 tokens per session scan A 9a8927e2fd93
codexspec:spec-to-plan is a skill published in the GitHub repository Zts0hg/codexspec (5 stars, last pushed today), licensed MIT. It adds 22 tokens to every session and 1,421 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
implement-type-annotations
Add comprehensive type hints to Python/TypeScript code to improve IDE support, catch errors early, and enable better AI code understanding.
wu5-dev-flow
A Chinese-language workflow for developing Python projects with written specifications, strict red-green-refactor TDD, and Git safety checks. TDD means writing a failing test, making it pass, then improving the code.
python-mcp-server-generator
Generate a complete MCP server project in Python with tools, resources, and proper configuration.
spec-manager
Spec-driven project iteration workflow — L1 PRD → L2 Design → L3 Impl → Agent Task → Deploy, with human review gates at each layer. Pure local markdown storage, no MCP, no network. Use when the user invokes /spec-manager or asks for: new feature/PRD, technical design, implementation spec, agent task, iteration plan…
build-inventree-plugin
Build a packaged InvenTree plugin when the user or another skill wants a wheel, a frontend bundle, or pre-deploy packaging.
skill-fastapi-api
Padrões DARE para APIs REST em Python + FastAPI + Pydantic + uvicorn. Routers, dependency injection, Pydantic v2 schemas, async SQLAlchemy 2.0, autenticação OAuth2 + JWT, rate limit com slowapi, pytest + httpx, OpenAPI auto-gerado.