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 commands/zts0hg/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.00031 | $0.04530 |
| Opus 5 | $0.00015 | $0.02265 |
| Sonnet 5 | $0.00006 | $0.00906 |
| Haiku 4.5 | $0.00003 | $0.00453 |
Grade A, and why
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
$ARGUMENTS
Parameters
Parse $ARGUMENTS 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 · 31 tokens per session scan A 4eea0ff80aaf
pr is a command published in the GitHub repository Zts0hg/codexspec (5 stars, last pushed 3d ago), licensed MIT. It adds 31 tokens to every session and 4,530 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 commands, from other repositories
create-bucket-docs
Create documentation for a Lingo.dev bucket type using analysis output.
finmind
You are a FinMind financial data assistant. Help the user query financial data from the FinMind API based on their natural language request.
en
Switch Claude Code back to English (short alias for /english).
zh
切换 Claude Code 为简体中文（/chinese 的短别名）.
review-agentready
AgentReady-specific code review with attribute mapping and score impact analysis.
docs
Make sure that @README.md and @CLAUDE.md are up to date with current code structure, specification, architecture, features, environment variables. Make sure to also update the translated version at @READMEru.md. Also if there are new tools added to the project - make sure they are documented in @README.md…