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 SetraTheXX/Codex-Engineering-Workflow-Pack --skill to-issuesgit clone --depth 1 https://github.com/SetraTheXX/Codex-Engineering-Workflow-PackWrote 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/setrathexx/codex-engineering-workflow-pack/to-issues)<a href="https://agentmods.dev/skills/setrathexx/codex-engineering-workflow-pack/to-issues"><img src="https://agentmods.dev/badge/skills/setrathexx/codex-engineering-workflow-pack/to-issues/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/setrathexx/codex-engineering-workflow-pack/to-issues"><img src="https://agentmods.dev/badge/skills/setrathexx/codex-engineering-workflow-pack/to-issues.svg" alt="Reviewed on agentmods" width="80" 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.00048 | $0.00941 |
| Opus 5.5 | $0.00019 | $0.00376 |
| Sonnet 5.5 | $0.00010 | $0.00188 |
| Haiku 4.5 | $0.00005 | $0.00094 |
Grade A, and why
to-issues 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 1mo 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 — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
To Issues
Break a PRD, plan, or feature document into small vertical slice issues that can be implemented without rediscovering the whole product context.
Default output is local markdown under docs/agents/issues/.
Remote issue publishing is optional and requires explicit user request.
Read First
Gather source material:
- PRD or plan path provided by the user,
- current conversation,
docs/agents/issue-tracker.md,docs/agents/domain.md,docs/agents/test-commands.md,CONTEXT.md,- relevant ADRs,
- existing issues if the repo already has local issue docs.
If the source PRD or plan is missing, ask for it. Do not invent scope.
Output Location
Default directory:
docs/agents/issues/
Recommended file naming:
0001-short-action-title.md
0002-short-action-title.md
If the repo already has a local issue convention, use it.
Before creating files:
- present the issue list,
- present target paths,
- ask for approval.
Workflow
1. Understand The Source
Summarize:
- product goal,
- acceptance criteria,
- constraints,
- known non-goals,
- verification expectations.
If source material conflicts with repo docs or ADRs, surface the conflict before slicing.
2. Draft Vertical Slices
Create slices that deliver narrow end-to-end value.
Each issue should usually include:
- user-visible or caller-visible behavior,
- data or state change if relevant,
- API, UI, CLI, or module surface if relevant,
- test or verification path,
- documentation update if needed.
Avoid horizontal layer issues such as:
- backend only,
- frontend only,
- tests only,
- schema only,
- refactor only,
- documentation only.
Exceptions are allowed only when a dependency is genuinely standalone, such as a migration prerequisite or shared test harness. Explain the exception.
See references/vertical-slice-guide.md.
3. Order And Dependencies
Order issues so each one can be implemented with minimal blocked work.
For each issue, identify:
What ships with it
2 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.
- 1mo ago First seen · 191 lines · 48 tokens per session scan A 49d9d89e0c2a
to-issues is a skill published in the GitHub repository SetraTheXX/Codex-Engineering-Workflow-Pack (1 stars, last pushed 28d ago), licensed MIT. It adds 48 tokens to every session and 941 once invoked, about $0.0002 per session on Opus 5.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
starting-a-new-project
Use when the workspace is empty, has no code, and the user brings a raw project idea. Normally reached via setting-up-a-project; not for an existing project.
pdlc-adopt
A tool for bringing an existing software project into a documented development process. It scans the project, identifies its services, applications, technologies, databases, and APIs, and can create baseline documents without changing code.
pdlc-status
A read-only progress overview for projects using PDLC, a documented process for moving a feature through stages such as design, testing, implementation, and review. It reads saved state files and groups work as ongoing, complete, or invalid.
pdlc-task
A task-tracking workflow for projects organized around a PRD, or product requirements document. It can split a feature into tasks and record each task as planned, active, completed, blocked, or reopened.
frappe-gameplan
Frappe Gameplan guidance for team discussions, projects, tasks, notes, decisions, async collaboration, permissions, and workspace workflows. Use when work touches Gameplan or planning/collaboration features in the Frappe ecosystem.
issue-fields-migration
Bulk-migrate metadata to GitHub issue fields from two sources: repo labels (e.g. priority labels to a Priority field) and Project V2 fields. Use when users say "migrate my labels to issue fields", "migrate project fields to issue fields", "convert labels to issue fields", "copy project field values to issue fields"…