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/mturac/everything-openai-codex/feature-devgit clone --depth 1 https://github.com/mturac/everything-openai-codexWrote 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/mturac/everything-openai-codex/feature-dev)<a href="https://agentmods.dev/commands/mturac/everything-openai-codex/feature-dev"><img src="https://agentmods.dev/badge/commands/mturac/everything-openai-codex/feature-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 | $0.00011 | $0.00253 |
| Opus 5 | $0.00005 | $0.00127 |
| Sonnet 5 | $0.00002 | $0.00051 |
| Haiku 4.5 | $0.00001 | $0.00025 |
Grade A, and why
feature-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 yesterday.
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.
This is a copy
100% identical to feature-dev — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
A structured feature-development workflow that emphasizes understanding existing code before writing new code.
Phases
1. Discovery
- read the feature request carefully
- identify requirements, constraints, and acceptance criteria
- ask clarifying questions if the request is ambiguous
2. Codebase Exploration
- use
code-explorerto analyze the relevant existing code - trace execution paths and architecture layers
- understand integration points and conventions
3. Clarifying Questions
- present findings from exploration
- ask targeted design and edge-case questions
- wait for user response before proceeding
4. Architecture Design
- use
code-architectto design the feature - provide the implementation blueprint
- wait for approval before implementing
5. Implementation
- implement the feature following the approved design
- prefer TDD where appropriate
- keep commits small and focused
6. Quality Review
- use
code-reviewerto review the implementation - address critical and important issues
- verify test coverage
7. Summary
- summarize what was built
- list follow-up items or limitations
- provide testing instructions
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.
- yesterday First seen · 50 lines · 11 tokens per session scan A b446c316f680
feature-dev is a command published in the GitHub repository mturac/everything-openai-codex (89 stars, last pushed 11d ago), licensed MIT. It adds 11 tokens to every session and 253 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to feature-dev, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
update-faq
could you please update DESIGNFAQ & DXFAQ based on the changes we are trying to achieve.
feature
Orchestrate a complete feature through discovery, spec, implementation, and review.
research
Research a technical or product question.
selfloop
Start or control a persistent SIPS loop whose only objective is improving SIPS and the agent operating it through measured, verified iterations.
dev-planner
Generate or update DEV-PLAN.md with phased development plan from Product-Spec.md.
patterns
Show the full agentpatterns report — success rate, approach→outcome correlation, top patterns.