Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/mturac/everything-openai-codexnpx agentmods add commands/mturac/everything-openai-codex/project-initWrote 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/project-init)<a href="https://agentmods.dev/commands/mturac/everything-openai-codex/project-init"><img src="https://agentmods.dev/badge/commands/mturac/everything-openai-codex/project-init/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/project-init"><img src="https://agentmods.dev/badge/commands/mturac/everything-openai-codex/project-init.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.00022 | $0.00926 |
| Opus 5.5 | $0.00009 | $0.00370 |
| Sonnet 5.5 | $0.00004 | $0.00185 |
| Haiku 4.5 | $0.00002 | $0.00093 |
Grade A, and why
project-init 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.
How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/project-init
Create a safe, reviewable ecc onboarding plan for the current project. This command should start in dry-run mode and only write files after explicit user approval.
Usage
/project-init
/project-init --dry-run
/project-init --target codex
/project-init --target cursor
/project-init --skills continuous-learning-v2,security-review
/project-init --config ecc-install.json
Safety Rules
- Default to dry-run. Do not modify
CODEX.md, settings files, rules, skills, or install state until the user approves the concrete plan. - Preserve existing project guidance. If
CODEX.md,.codex/settings.local.json,.cursor/,.codex/,.gemini/,.opencode/,.codebuddy/,.joycode/, or.qwen/already exists, inspect it and propose a merge/append plan instead of overwriting. - Use ecc's installer and manifest tooling. Do not hand-copy files or clone arbitrary remotes as an install shortcut.
- Keep permissions narrow. Any generated settings should match detected build/test/lint tools and avoid broad shell access.
- Report exactly what would change before applying anything.
Detection Inputs
Read the current project root and detect stack signals from:
- package manager files:
package.json,package-lock.json,pnpm-lock.yaml,yarn.lock,bun.lockb - language manifests:
pyproject.toml,requirements.txt,go.mod,Cargo.toml,pom.xml,build.gradle,build.gradle.kts - framework files:
next.config.*,vite.config.*,tailwind.config.*,Dockerfile,docker-compose.yml - ecc config:
ecc-install.json - optional stack map:
config/project-stack-mappings.jsonin the ecc repo
When the ecc checkout is available, use config/project-stack-mappings.json as the stack-to-rules/skills reference. If the file is unavailable, fall back to the installed ecc manifests and explicit user choices.
Planning Flow
- Identify the target harness. Default to
codexunless the user asks forcursor,codex,gemini,opencode,codebuddy,joycode, orqwen. - Detect stacks from project files and show the evidence for each match.
- Resolve the smallest useful ecc plan:
- project has an
ecc-install.json:node scripts/install-plan.js --config ecc-install.json --json - user named a profile:
node scripts/install-plan.js --profile <profile> --target <target> --json - user named skills:
node scripts/install-plan.js --skills <skill-ids> --target <target> --json - only language stacks are detected: use the legacy language install dry-run with those language names
- project has an
- Run a dry-run apply command before writing:
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 · 87 lines · 22 tokens per session scan A d878af3cc8c2
project-init is a command published in the GitHub repository mturac/everything-openai-codex (86 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 926 once invoked, about $0.0001 per session on Opus 5.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
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.