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.
git 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/plan)<a href="https://agentmods.dev/commands/mturac/everything-openai-codex/plan"><img src="https://agentmods.dev/badge/commands/mturac/everything-openai-codex/plan/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/mturac/everything-openai-codex/plan"><img src="https://agentmods.dev/badge/commands/mturac/everything-openai-codex/plan.svg" alt="Reviewed on agentmods" width="80" 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.00006 | $0.00286 |
| Opus 5.5 | $0.00002 | $0.00114 |
| Sonnet 5.5 | $0.00001 | $0.00057 |
| Haiku 4.5 | $0.00001 | $0.00029 |
Grade A, and why
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 1mo 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.
This is a copy
86% identical to plan — 69 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
Plan Command
Create a detailed implementation plan for: $ARGUMENTS
Your Task
- Restate Requirements - Clarify what needs to be built
- Identify Risks - Surface potential issues, blockers, and dependencies
- Create Step Plan - Break down implementation into phases
- Wait for Confirmation - MUST receive user approval before proceeding
Output Format
Requirements Restatement
[Clear, concise restatement of what will be built]
Implementation Phases
[Phase 1: Description]
- Step 1.1
- Step 1.2 ...
[Phase 2: Description]
- Step 2.1
- Step 2.2 ...
Dependencies
[List external dependencies, APIs, services needed]
Risks
- HIGH: [Critical risks that could block implementation]
- MEDIUM: [Moderate risks to address]
- LOW: [Minor concerns]
Estimated Complexity
[HIGH/MEDIUM/LOW with time estimates]
WAITING FOR CONFIRMATION: Proceed with this plan? (yes/no/modify)
CRITICAL: Do NOT write any code until the user explicitly confirms with "yes", "proceed", or similar affirmative response.
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.
- 1mo ago First seen · 50 lines · 6 tokens per session scan A e292d2864087
plan is a command published in the GitHub repository mturac/everything-openai-codex (86 stars, last pushed 1mo ago), licensed MIT. It adds 6 tokens to every session and 286 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 86% identical to plan, differing in 69 lines, and is treated as a copy.
Other commands, from other repositories
morning
The coffee report — cross-project map deltas, arrives on its own (scheduled).
handoff
Refresh the project hand-off before ending the session.
convert-to-plan
Convert planning artifacts (lite-plan, workflow session, markdown) to issue solutions.
execute
Execute queue with DAG-based parallel orchestration (one commit per solution).
queue
Form execution queue from bound solutions using issue-queue-agent (solution-level).
from-brainstorm
Convert brainstorm session ideas into issue with executable solution for parallel-dev-cycle.