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/auto-devgit 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/commands/zts0hg/codexspec/auto-dev)<a href="https://agentmods.dev/commands/zts0hg/codexspec/auto-dev"><img src="https://agentmods.dev/badge/commands/zts0hg/codexspec/auto-dev.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.00011 | $0.01864 |
| Opus 5 | $0.00005 | $0.00932 |
| Sonnet 5 | $0.00002 | $0.00373 |
| Haiku 4.5 | $0.00001 | $0.00186 |
Grade A, and why
auto-dev 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Continuous Blueprint Development
Language Preference
Read .codexspec/config.yml. Converse in language.interaction and author SDD artifacts in
language.document, each falling back to language.output, then English.
Goal
Continuously run the complete Requirements-First SDD flow for the shared blueprint in document
order. Requirements in the blueprint are already confirmed. Do not ask the user to reconfirm them,
perform new requirements discovery, or depend on workflow.auto_next.
Run Ownership and Finalization
- Run
codexspec _auto-dev-helper acquirewith{}on stdin. If another live run owns the repository, report it and exit immediately without waiting. - Keep the returned opaque
token. Runrenewbefore and after each stage and tool operation. If an operation can run longer than the returnedheartbeat_interval_seconds, keep callingrenewat that interval until it finishes. Runassert-ownerimmediately before every repository mutation. Never reuse a token after an ownership failure. - Inspect the returned
merge_recovery. When it reportsneeds_resolution, this run has fenced an interrupted synchronization merge to its new token; edit every conflicted file and callprepare-sync-verificationwith the token and the exact completeresolved_pathslist before running checks. When it reportsneeds_verification, use the existing merge result as the verification candidate. Run the project's required baseline checks and callcontinue-sync, or callabort-syncif conflict preparation or a passing baseline cannot be completed. Then repeatsync-defaultuntil it returnsclean, and run the baseline checks once more before selecting any requirement. - On every normal success or controlled stop, call
releasein finalization. An unexpected termination is recovered by stale-owner reclamation on the next invocation. blueprintremains allowed while this run is active; do not hold a blueprint or Git lock while interpreting documents or implementing code.
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 · 149 lines · 11 tokens per session scan A 8c5b8c844e91
auto-dev is a command published in the GitHub repository Zts0hg/codexspec (5 stars, last pushed 4d ago), licensed MIT. It adds 11 tokens to every session and 1,864 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-09-03.
Other commands, from other repositories
add-performance-monitoring
Setup application performance monitoring.
review
Review the current diff for violations of the conventions in AGENTS.md and .cursor/rules/. Report findings ordered by severity; do not fix anything unless asked.
organize-files
Organize and rename files based on content analysis.
quick-fix
Fast-track workflow for small bug fixes.
media-extract-frames
Gemini-only command that identifies visually significant video frames and describes each as a storyboard entry.
help
Category: System Syntax: /help [command|topic].