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/skyloevil/codex-sdd/continuenpx skills add skyloevil/codex-sdd --skill continuegit clone --depth 1 https://github.com/skyloevil/codex-sddWhat 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.00025 | $0.00483 |
| Opus 5 | $0.00013 | $0.00242 |
| Sonnet 5 | $0.00005 | $0.00097 |
| Haiku 4.5 | $0.00003 | $0.00048 |
Grade A, and why
codex-sdd:continue 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 — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenSpec Continue
Context
Continue is the high-level entry point for a smooth Codex App workflow. It uses the state machine to decide what should happen next, instead of requiring the user to remember propose/plan/implement/validate/archive commands.
Workflow
- Call
openspec_get_goal. - If there is an active change but no useful loop objective, call
openspec_create_goalusing the change proposal/next action as the objective and the acceptance criteria assuccessCriteria. - Call
openspec_continue_loopand follow the returneddecision. - If
decision.kindisask_human, summarize the pending review, the gate, and the risk. Wait for approval before callingopenspec_resolve_human_review. - If
decision.kindisact, readtaskswithopenspec_read_artifact, implement the referenced task, callopenspec_record_iteration, run focused checks, callopenspec_record_validation_evidence, then callopenspec_update_taskonly after evidence exists or the user explicitly accepts a pending validation state. - If
decision.kindisvalidate, callopenspec_validate, run relevant checks, record evidence, fix drift, and request/resolve the validation gate when clean. - If
decision.kindisrun_hook, execute or ask for the required hook based on its policy, then callopenspec_record_hook_result. - If
decision.kindisarchive, callopenspec_archive_change. - If
decision.kindiscompleteorblocked, report the final loop state.
Human Gates
Confirm at scope, design, validation, archive, and before destructive work: file deletion, public API changes, database schema changes, broad refactors, or external-system writes.
Automatically request a human review with openspec_request_human_review when
requirements are ambiguous, validation repeatedly fails, required hooks fail,
or a step would perform destructive changes, public API changes, database schema
changes, security-sensitive changes, or external-system writes.
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 · 43 lines · 25 tokens per session scan A 0379dfa4a1d3
codex-sdd:continue is a skill published in the GitHub repository skyloevil/codex-sdd (1 stars, last pushed 1mo ago), licensed MIT. It adds 25 tokens to every session and 483 once invoked, about $0.0001 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
codexkit-repository-maintenance
Use when maintaining or improving the GameStudio-CodexKIT source repository, including CI, governance, catalog, generators, adapters, packaging, documentation, versioning, or release readiness.
unity-ui-art-and-motion-production
Use when new or revised Unity UI visuals, icons, panels, 9-slice sprites, component states, HUD or menu layouts, popup motion, screen transitions, or flattened UI screenshot decomposition must be produced through Figma and integrated into uGUI, NGUI, or UI Toolkit; not for UI debugging, localization-only work…
game-screenshot-showcase-and-store-packaging
Use when a Unity team needs approved PlayMode screenshots, immutable capture evidence, reviewed showcase slides, or report-only store screenshot packaging without auto-upload, signing, or submission.
studio-project-scaffold
Use when running gamestudio init, status, or uninit, or bootstrapping a new or adopted game repository with AGENTS.md, HANDOFF.md, .agents/CONTRACT.md, project governance, a subsystem registry, or a per-project adapter report, plan digest, named reviewer, backup root, generated agent overlay, apply, uninstall, and…
using-game-studio-skills
Use when starting any GameStudio-CodexKIT task or when a model runner is unavailable and someone requests a confidence-based PASS.
skill-authoring-and-audit
Use when creating or revising a GameStudio-CodexKIT skill, resolving ambiguous skill triggers, auditing provenance or lifecycle maturity, or deriving reusable capabilities from session history.