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/prototypenpx skills add SetraTheXX/Codex-Engineering-Workflow-Pack --skill prototypegit 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.00049 | $0.00881 |
| Opus 5 | $0.00024 | $0.00441 |
| Sonnet 5 | $0.00010 | $0.00176 |
| Haiku 4.5 | $0.00005 | $0.00088 |
Grade A, and why
prototype 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 yesterday.
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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prototype
Use a prototype to answer a question quickly before changing production behavior.
A prototype is temporary. It should have a clear question, success criteria, and exit decision.
Read First
Inspect relevant context:
docs/agents/domain.mddocs/agents/test-commands.mdCONTEXT.md- relevant ADRs under
docs/adr/ - existing UI routes, components, modules, tests, or scripts near the idea
If setup docs are missing, infer local conventions from the repo and say what is unknown.
Choose Prototype Type
Pick one:
Logic Prototype
Use when the question is about:
- state transitions,
- business rules,
- validation behavior,
- data transformations,
- edge cases,
- algorithm shape.
Typical shape: a small local script, REPL-friendly module, or isolated route through existing public functions.
UI Prototype
Use when the question is about:
- layout,
- interaction flow,
- component composition,
- navigation,
- visual variants,
- user feedback states.
Typical shape: a temporary route, page, story, or local-only component variant.
If the type is ambiguous, recommend one and explain why.
Workflow
1. Define The Experiment
State:
- question being answered,
- prototype type,
- audience or actor,
- success criteria,
- constraints,
- what will not be tested.
If success criteria are unclear, ask the user before creating files.
2. Inspect Local Conventions
Find where a temporary prototype would fit without confusing production code.
Look for:
- existing scripts,
- playground routes,
- storybook stories,
- examples directories,
- test fixtures,
- local-only dev pages.
Do not invent a new convention when the repo already has one.
3. Propose Path And Command
Before writing, propose:
- files to create,
- files to touch,
- how to run it,
- how it will be marked temporary,
- how it will be removed or promoted.
Ask for approval before creating files.
4. Build Small
When approved:
- keep state local unless persistence is the experiment,
- avoid production integration by default,
- mark temporary files clearly,
- expose relevant state in the UI or console,
- skip polish that does not answer the question,
- avoid new dependencies unless approved.
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.
- yesterday First seen · 176 lines · 49 tokens per session scan A 579c03438ce6
prototype is a skill published in the GitHub repository SetraTheXX/Codex-Engineering-Workflow-Pack (1 stars, last pushed yesterday), licensed MIT. It adds 49 tokens to every session and 881 once invoked, about $0.0002 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.
reviewing-changes
Use when a review package asks you to review a plan step's change set (todo.startReview): you are the REVIEWER, not the author. How to judge an agent-written diff, file findings with addreviewcomment, and settle with exactly one reviewverdict.
asking-user-questions
Use when composing an askuserquestion round inside a workflow, or when a workflow skill names it at a question step. Shared norms for the tool — not a workflow, nothing to execute.
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.