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/zoom-outnpx skills add SetraTheXX/Codex-Engineering-Workflow-Pack --skill zoom-outgit 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/zoom-out)<a href="https://agentmods.dev/skills/setrathexx/codex-engineering-workflow-pack/zoom-out"><img src="https://agentmods.dev/badge/skills/setrathexx/codex-engineering-workflow-pack/zoom-out.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.1 | $0.00048 | $0.00834 |
| Opus 5 | $0.00024 | $0.00417 |
| Sonnet 5 | $0.00010 | $0.00167 |
| Haiku 4.5 | $0.00005 | $0.00083 |
Grade A, and why
zoom-out 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.
How it starts
The opening of the file, as written. The whole thing — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Zoom Out
Map an unfamiliar code area before changing it.
This skill is read-only. Do not refactor, edit files, create docs, or start implementation while using it.
Read First
Inspect project context:
docs/agents/domain.mdCONTEXT.md- relevant ADRs under
docs/adr/ docs/agents/test-commands.md- files or modules named by the user
- callers, callees, tests, routes, commands, or API surfaces around the target area
Use fast search when possible:
rg --files
rg "<symbol-or-term>"
Keep Windows paths with spaces quoted when showing file locations.
When To Use
Use when:
- the user says they do not know an area,
- a bug or feature touches unfamiliar code,
- implementation risk comes from unclear module relationships,
- a repo has many small files and no obvious entry point,
- the next skill needs orientation before acting.
Do not use this for confirmed implementation tasks unless orientation is still missing.
Workflow
1. Define The Focus
Identify the area to map:
- file,
- folder,
- module,
- route,
- command,
- API endpoint,
- domain term,
- failing test,
- user-visible behavior.
If the focus is too broad, narrow it to the smallest useful area and state the assumption.
2. Find Entry Points
Look for how the area is reached:
- public exports,
- route handlers,
- CLI commands,
- UI screens,
- scheduled jobs,
- tests,
- integration points.
List the main entry points before diving into internals.
3. Map Callers And Callees
Trace:
- who calls this code,
- what this code calls,
- data flowing in,
- data flowing out,
- side effects,
- error paths,
- state transitions.
Keep the map high signal. Do not list every helper unless it changes understanding.
4. Connect Domain Language
Use repo vocabulary.
Report:
- domain terms involved,
- ambiguous terms,
- terms used differently in code and docs,
- missing terms that may need
grill-with-docs.
Do not invent certainty. Mark uncertainty clearly.
5. Check Decisions And Tests
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.
- 5d ago First seen · 167 lines · 48 tokens per session scan A 309f50053601
zoom-out is a skill published in the GitHub repository SetraTheXX/Codex-Engineering-Workflow-Pack (1 stars, last pushed 4d ago), licensed MIT. It adds 48 tokens to every session and 834 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-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.
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-workflow-thinking
Sequential Thinking MCP for structured step-by-step analysis via --deepthink flag. Separate from UltraThink which is Claude's native extended reasoning mode. Use for multi-step analysis or architecture decisions.
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…