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/reflect-codex-workflowsnpx skills add WildPigKing/codex-project-skill-manager --skill reflect-codex-workflowsgit 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/reflect-codex-workflows)<a href="https://agentmods.dev/skills/wildpigking/codex-project-skill-manager/reflect-codex-workflows"><img src="https://agentmods.dev/badge/skills/wildpigking/codex-project-skill-manager/reflect-codex-workflows.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.00051 | $0.00303 |
| Opus 5 | $0.00026 | $0.00151 |
| Sonnet 5 | $0.00010 | $0.00061 |
| Haiku 4.5 | $0.00005 | $0.00030 |
Grade A, and why
reflect-codex-workflows 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 5d 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
Reflect Codex Workflows
Review the objective, constraints, artifacts, corrections, failures, and verification evidence. Extract only lessons that could change execution in another project.
Read the repository skills menu first. When the user requests cross-project comparison, read the relevant user-level skills menu and only the shortlisted user SKILL.md files; do not scan the broader user home. For each distinct reflection task, shortlist at most three close skills and compare:
- trigger and task boundary;
- required inputs and environment;
- decision rules and ordering;
- completion and validation criteria;
- failure recovery;
- reusable scripts or references.
Choose one result:
- Reuse when an existing skill already covers the workflow.
- Revise when the boundary is the same and evidence adds a durable rule or validation method.
- Create when the trigger or completion contract is materially distinct.
- Do not skill when the lesson is project-specific, obvious, or unsupported.
Report the evidence, closest skill, marginal benefit, proposed trigger, one realistic validation scenario, and details that should not be generalized.
Ask before editing. When authorized, preserve user intent, keep the skill concise, update the registry, regenerate the menu, validate format, and label untested behavior honestly.
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.
- 5d ago First seen · 29 lines · 51 tokens per session scan A 3a7cc2db65af
reflect-codex-workflows is a skill published in the GitHub repository WildPigKing/codex-project-skill-manager (22 stars, last pushed 9d ago), licensed MIT. It adds 51 tokens to every session and 303 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
sv
This skill should be used when the user invokes /sv or asks to "hand this off to sandvault", "continue in the sandbox", "sandvault this task", or to clone the current repo into a sandboxed Claude session with per-repo deploy-key access. Writes a task briefing to the sandvault shared workspace and launches sv-clone in…
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…