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/setrathexx/codex-engineering-workflow-pack/setup-codex-engineering-workflownpx skills add SetraTheXX/Codex-Engineering-Workflow-Pack --skill setup-codex-engineering-workflowgit clone --depth 1 https://github.com/SetraTheXX/Codex-Engineering-Workflow-PackWhat 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.00054 | $0.01307 |
| Opus 5 | $0.00027 | $0.00654 |
| Sonnet 5 | $0.00011 | $0.00261 |
| Haiku 4.5 | $0.00005 | $0.00131 |
Grade A, and why
setup-codex-engineering-workflow 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 2d 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 — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup Codex Engineering Workflow
Set up the repo-local context that the other workflow skills read before planning, debugging, testing, issue writing, or handoff.
This skill is local-first. Prefer markdown files in the current repo. Treat GitHub or any remote issue tracker as optional, never required.
What This Skill Produces
When approved by the user, create or update repo-local guidance under docs/agents/.
Default layout:
docs/agents/
issue-tracker.md
domain.md
test-commands.md
handoff.md
issues/
docs/adr/
CONTEXT.md
Do not overwrite existing configuration without showing the planned changes first.
Read First
Inspect the repo before asking questions.
Look for:
- Package manager files:
package.json, lockfiles,pyproject.toml,requirements.txt,Cargo.toml,go.mod, or similar. - Existing scripts: test, typecheck, lint, format, e2e, dev.
- Existing docs:
README.md,docs/,CONTEXT.md,docs/adr/,specs/,plans/. - Existing issue conventions:
docs/agents/issues/,.scratch/,issues/,.github/ISSUE_TEMPLATE/. - Existing handoff notes:
docs/agents/handoffs/,handoffs/, temp notes, or project docs. - Git remote only as a clue. Do not assume GitHub issues are the tracker.
Use fast search commands when available:
rg --files
Decision Model
Make recommendations from repo evidence. Ask the user only when the answer cannot be inferred safely.
Decisions to establish:
- Issue tracker
- Docs directory
- ADR directory
- Domain language document
- Test commands
- Package manager
- Agent handoff directory
- Local issue directory
Default choices:
- Issue tracker: local markdown.
- Docs directory:
docs/agents/. - ADR directory:
docs/adr/. - Domain language document:
CONTEXT.md. - Handoff directory:
docs/agents/handoffs/. - Local issue directory:
docs/agents/issues/.
Workflow
1. Explore
Read the current repo structure and existing docs.
Produce a short findings list:
What ships with it
3 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.
- 2d ago First seen · 202 lines · 54 tokens per session scan A de2c26acc711
setup-codex-engineering-workflow is a skill published in the GitHub repository SetraTheXX/Codex-Engineering-Workflow-Pack (1 stars, last pushed 2d ago), licensed MIT. It adds 54 tokens to every session and 1,307 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-31.
Other skills, from other repositories
todos
This chat has a shared, live TODO plan — your tasks for the conversation, which the user also edits. Read this skill and reach for the todo tools whenever a request takes more than a couple of steps. It covers the plan model (group = task, items = its steps; loose items are the user's lane), how to work it: propose…
writing-workflow-skills
Use when adding a new workflow skill to pi-thinkrail-workflow, changing an existing workflow skill's role, trigger, handoff, or structure, or checking a workflow skill against the workflow system's rules. Not for authoring general-purpose skills outside this package.
brainstorming
Use this BEFORE any creative or feature work: building a new feature, adding functionality, changing behavior, or making a nontrivial design decision. Turns the user's request into a validated design — recorded as a spec-graph task-spec — before any implementation. Do not skip this because a change looks small.
shipping-a-pr
Use when finished work needs to ship as a pull request, or when the ask is about a PR — creating one, bringing it up to date, adding screenshots, watching its checks, or addressing its review comments. Not for reviewing a PR you are not shipping.
setting-up-a-project
Use whenever asked to set up, onboard, initialize, or spec a project — the front door when the workspace has no spec graph yet (brand-new or an existing codebase); also seeded by the app's Set-up-project card (/skill:setting-up-a-project). Not for feature work in an already-specced project — use the brainstorming…
writing-specs
Use when a workflow step drafts or revises a spec artifact — a goal-and-requirements, an architecture, or a module SPEC — or when a workflow skill names it at such a step. The shared quality bar for specs — not a workflow, nothing to execute.