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 skills/wildpigking/codex-project-skill-manager/organize-codex-projectsnpx skills add WildPigKing/codex-project-skill-manager --skill organize-codex-projectsgit clone --depth 1 https://github.com/WildPigKing/codex-project-skill-managerWrote 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/skills/wildpigking/codex-project-skill-manager/organize-codex-projects)<a href="https://agentmods.dev/skills/wildpigking/codex-project-skill-manager/organize-codex-projects"><img src="https://agentmods.dev/badge/skills/wildpigking/codex-project-skill-manager/organize-codex-projects.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.00052 | $0.00257 |
| Opus 5 | $0.00026 | $0.00129 |
| Sonnet 5 | $0.00010 | $0.00051 |
| Haiku 4.5 | $0.00005 | $0.00026 |
Grade A, and why
organize-codex-projects 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 6d 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.
What it actually says
Organize Codex Projects
Resolve the approved future-projects root before creating anything.
For a focused project, create AGENTS.md, README.md, data, temp, output, docs/ai/dev_log.md, and docs/ai/experience_candidates.md. Add src and tests only when code benefits from them.
Use an umbrella project only when two or more workstreams have meaningfully independent goals, inputs, outputs, or lifecycles. Keep shared material at the umbrella root and give each durable subproject its own README, data, temp, and output boundary. File count alone is not a reason to split.
Use concise purpose-derived names. Do not add date wrappers, random abbreviations, final, or numeric collision suffixes. If a target exists and reuse is unclear, stop and ask.
Keep original inputs in data, reproducible intermediates in temp, and current deliverables in output. Never silently overwrite source material.
Return the resolved absolute target and a structure preview before writing.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 19 lines · 52 tokens per session scan A cb61551432b5
organize-codex-projects is a skill published in the GitHub repository WildPigKing/codex-project-skill-manager (22 stars, last pushed 10d ago), licensed MIT. It adds 52 tokens to every session and 257 once invoked, about $0.0003 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-30.
Other skills, from other repositories
codex-prompt
Generate structured, self-contained Codex task prompts. Use when the user asks for a Codex prompt, delegation task, fix, build, audit, ops/tuning, refactor, PR-series, or master-session brief to hand to another Codex run. Grounds every cited path and command, distinguishes directive from investigative work, and binds…
retro-distill
Run a self-distillation retrospective on recent OpenAI Codex sessions (or any Agent-Skills-compatible agent). Use when the user says 'retro,' 'retrospective,' 'distill,' 'what did we learn,' 'review sessions,' 'self-improve,' or after completing a major chunk of work. Covers three modes: quick retro (single session)…
eco-max
Maximum-savings variant of eco - the same frugality rules with a tighter reply budget, for routine chores (rename, small fix, quick lookup, boilerplate). Prefer plain eco for hard or high-stakes work. Works in any language.
gate-engineering
Design, implement, review, or repair durable quality gates such as linters, CI checks, tripwires, corpus detectors, contract suites, and snapshot or golden tests. Use when asked to add a check that catches a defect, when a recurring defect needs class-wide prevention, when a gate is being trusted or recalibrated, or…
git-under-contention
Operate Git safely when multiple humans or coding agents may share a repository, checkout, index, branches, or worktrees. Use before staging, committing, pushing, merging, rebasing, creating or removing worktrees, recovering apparently lost edits, handling staged files you did not touch, or preserving unfinished agent…
session-close
Close a coding-agent session with durable repository state, proportional verification, documentation reconciliation, and a useful handoff. Use when the user says close out, wrap up, end session, session report, doc sync, preserve work, or asks for a final commit and push before stopping.