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 skills add Phelan164/codex-howto --skill maintain-codex-wikigit clone --depth 1 https://github.com/Phelan164/codex-howtoWrote 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/phelan164/codex-howto/maintain-codex-wiki)<a href="https://agentmods.dev/skills/phelan164/codex-howto/maintain-codex-wiki"><img src="https://agentmods.dev/badge/skills/phelan164/codex-howto/maintain-codex-wiki.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.00076 | $0.02351 |
| Opus 5 | $0.00038 | $0.01175 |
| Sonnet 5 | $0.00015 | $0.00470 |
| Haiku 4.5 | $0.00008 | $0.00235 |
Grade A, and why
maintain-codex-wiki 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 7d 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 — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Maintain Codex Wiki
Treat the wiki as compiled maintainer knowledge, not as an automatic source of truth. Keep official documentation authoritative and require human review before shared knowledge or curriculum changes land.
Choose one operation
- Query: read
knowledge/index.md, search candidate pages, and answer with links. Do not write unless the user explicitly asks. - Capture: preserve a durable lesson from repository evidence such as a merged change, incident, review finding, or measured run.
- Ingest: register one source, update affected wiki pages, run lint, and prepare a reviewable diff.
- Archive: save a requested query result as an experimental, cited page.
- Lint: run the bundled deterministic checker, then review semantic drift that a script cannot prove.
- Promote: move a verified conclusion into the appropriate module, skill, or repository rule through a separate, reviewable change.
Confinement invariant
Apply this before any operation reads, searches, or changes wiki state. For every wiki page, index, registry, log, cache target, and working-tree repository file inspected while capturing new evidence:
- require a normalized project-relative path;
- reject absolute paths and
..components; - resolve symlinks;
- for an existing read or update target, reject a symlink at the target or any parent below the project root, require a regular file, and verify the resolved target remains inside the project root; and
- for a new page, require a nonexistent target under an existing, project-contained directory, reject symlinked parents and name collisions, then repeat the existing-file check immediately after creation.
Do not begin Query, Capture, Ingest, Archive, Lint, or Promote until every file the operation will touch passes the applicable check. Treat an unsafe path as a reported validation error, never as content to inspect.
A revision-bound registered repository path is not a working-tree read.
Validate its normalized project-relative name, sensitivity, trusted commit, and
regular-file entry in the pinned Git tree, then read that immutable blob. Do not
require the path to exist in the current checkout: durable evidence remains
valid after a later rename or deletion. Set GIT_NO_LAZY_FETCH=1 on every Git
object probe and read so a partial clone cannot contact its promisor remote
without explicit network authorization. Also set GIT_NO_REPLACE_OBJECTS=1 so
local replacement refs cannot substitute different commits or blobs for the
recorded object IDs.
What ships with it
4 files 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.
- 7d ago First seen · 241 lines · 76 tokens per session scan A 003e82a0cce1
maintain-codex-wiki is a skill published in the GitHub repository Phelan164/codex-howto (3 stars, last pushed 2d ago), licensed MIT. It adds 76 tokens to every session and 2,351 once invoked, about $0.0004 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-31.
Other skills, from other repositories
boss-briefing
Vault health check — workflow pattern analysis, profile sync, session gap recovery, persona rule proposals.
briefing-vault
Initialize, manage, and search the per-project .briefing/ vault. Obsidian-compatible persistent knowledge base.
ctxwise
Audit and optimize OpenAI Codex context locally, compile model and subagent profiles, detect capability drift, create redacted lockfiles, inspect model-visible prompt structure, and render honest token, credit, quota, or API-cost receipts. Use when the user explicitly invokes CtxWise or asks to run its installed CLI…
handover
Use when wrapping up or capturing the current state of a coding session — writes a short, dated entry to the repo's RepoHandover.md so a future agent or you can resume without grepping archived sessions. Triggers on "handover", "hand off", "write handover", "capture state", "checkpoint this session".
obsidian-memory
Cross-project long-term memory over an Obsidian brain vault: recall relevant notes before a task, and persist distilled conclusions (decisions, pitfalls, solutions, progress) back after a task. The vault is an optional aggregation/projection layer — repo-local artifacts stay the per-project source of truth, and sync…
compact-kb
Use only when user explicitly invokes $compact-kb.