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/to-issuesnpx 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.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.00048 | $0.00941 |
| Opus 5 | $0.00024 | $0.00470 |
| Sonnet 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 3d 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.
- 3d 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 3d ago), licensed MIT. It adds 48 tokens to every session and 941 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
hns-lsel-curator
Local Self-Evolution Loop (LSEL) curator — the CLUSTER + drain engine for the GOOS-local PROPOSE→APPLY seam closure (SPEC-LSEL-LOCAL-EVOLUTION-001). Companion-offset drain of .moai/lessons-inbox.jsonl with a drain-side severity filter that drops the 65% Bash-timeout/sandbox noise, eventkey clustering with a frequency…
hns-workflow-ci-loop
Unified CI watch + auto-fix loop skill. Polls gh pr checks after /moai sync PR creation, classifies required vs auxiliary failures, attempts safe automated patches (max 3 iterations), and escalates semantic failures to the user. Use for CI loop workflow — NOT for general loop iteration patterns (see…
moai-kanban-foreman
One unattended kanban foreman iteration: watch the backlog queue, dispatch the next operator-picked card to an isolated worker, collect completion evidence on read (not on claims), and report. This is the body the project's loop.md driver invokes each iteration of a bare /loop; it can also be invoked directly to test…
moai-harness-learner
Harness learning subsystem coordinator. Produces Tier 4 auto-update proposal payloads consumed by the orchestrator (which surfaces them via AskUserQuestion) and orchestrates Apply/Rollback flows. Triggers when harness learning proposals are pending or learning lifecycle management is needed.
hns-oss-docs-readme-sync
README 4-file synchronization procedure for the oss-docs harness: Korean README.ko.md as primary source, en/ja/zh derivation, the shared language-switcher header contract, section-order parity checklist, and the manual verification recipe (no linter exists for READMEs). Loaded by the content-author and…
moai-domain-humanize
AI text humanization and 윤문 (post-editing) specialist that detects and removes AI tells while preserving meaning, facts, and figures. Covers Korean, English, Japanese, and Chinese with a shared severity model (S1/S2/S3), quality grades (A/B/C/D), and 30%/50% over-editing guardrails. Use to make AI-generated text read…