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/zts0hg/codexspec/codexspec-prnpx skills add Zts0hg/codexspec --skill codexspec-prgit clone --depth 1 https://github.com/Zts0hg/codexspecWhat 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.00037 | $0.04513 |
| Opus 5 | $0.00018 | $0.02256 |
| Sonnet 5 | $0.00007 | $0.00903 |
| Haiku 4.5 | $0.00004 | $0.00451 |
Grade A, and why
codexspec:pr 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 2d 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 — 635 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Constitution Compliance (MANDATORY)
Before generating PR description:
- Check for Constitution File: Look for
.codexspec/memory/constitution.md - If Constitution Exists:
- Load and read relevant principles (especially documentation standards, code review guidelines)
- Ensure PR description reflects constitutional principles
- Verify that the changes align with project quality standards
- If No Constitution Exists: Proceed with standard PR generation
Language Preference
IMPORTANT: Before generating PR descriptions, read the project's language configuration from .codexspec/config.yml.
PR description language priority:
- If
language.commitis set, use that language for the PR description - Otherwise, use
language.outputas fallback - If neither is configured, default to English
Note:
- Technical terms (e.g., API, JWT, OAuth, PR, MR) may remain in English when appropriate
- The PR title and section headers should follow the configured language
Examples:
output: "zh-CN"+commit: "en"→ Chinese interactions, English PR descriptionsoutput: "zh-CN"+commit: "zh-CN"→ Chinese for bothoutput: "zh-CN"+ nocommitsetting → Chinese for both (fallback)
User Input
the text after the $codexspec:pr skill mention
Parameters
Parse the text after the $codexspec:pr skill mention for the following optional parameters:
| Parameter | Default | Description |
|---|---|---|
--target-branch <branch> |
origin/main |
Branch to compare against |
--output <file> |
(none) | Save output to file instead of terminal |
--sections <list> |
all |
Comma-separated sections to include |
--spec <path> |
(none) | Enable spec.md integration (opt-in) |
--sections Values
summary- High-level overview of changeschanges- Detailed file changes and technical approachtesting- Test coverage informationverify- Verification stepschecklist- Pre-merge checklistnotes- Additional notes and breaking changesall- Include all sections (default)
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.
- 2d ago First seen · 635 lines · 37 tokens per session scan A 9bb0307f69f1
codexspec:pr is a skill published in the GitHub repository Zts0hg/codexspec (5 stars, last pushed 4d ago), licensed MIT. It adds 37 tokens to every session and 4,513 once invoked, about $0.0002 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
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…
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…
spec-manager
Spec-driven project iteration workflow: L1 PRD -> L2 Design -> L3 Impl -> Agent Task, with human review gates at each layer.
comet-native
Comet Native 工作流。当用户明确调用 /comet-native、要求启动或恢复 Native change，或入口路由到 Native 时使用。.
comet-design
Comet Classic 阶段 2 —— 为 change 产出深度技术 Design Doc。.
bug-triage
Read all open bugs in production/qa/bugs/, re-evaluate priority vs. severity, assign to sprints, surface systemic trends, and produce a triage report. Run at sprint start or when the bug count grows enough to need re-prioritization.