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/archivenpx skills add skyloevil/codex-sdd --skill archivegit 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.00033 | $0.00816 |
| Opus 5 | $0.00016 | $0.00408 |
| Sonnet 5 | $0.00007 | $0.00163 |
| Haiku 4.5 | $0.00003 | $0.00082 |
Grade A, and why
codex-sdd:archive 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenSpec Archive
Context
Archive is the final phase of the OpenSpec workflow. It preserves the change artifacts (proposal, design, tasks) into a structured archive directory and updates the knowledge base for future reference. This is the "accumulate experience" step.
Trigger
Any of these patterns triggers this skill:
- User says "openspec archive" or "openspec:archive"
- Validation passed and user wants to finalize
openspec_get_statusshows phase isvalidateorarchiveand ready to archive- User manually requests archiving
Prerequisites
- Validation passed (or user explicitly wants to archive without validation)
- All spec files exist
Workflow
Step 1: Prepare Archive
Call openspec_get_status to confirm the change is ready for archiving.
Check that all key artifacts are present:
openspec/changes/<changeId>/proposal.mdopenspec/changes/<changeId>/tasks.mdopenspec/changes/<changeId>/verification.mdopenspec/changes/<changeId>/implementation-notes.md
Step 2: Confirm with User
Gate: Archive Confirmation — Ask:
- "Archive change [changeId]? This will store the spec documents and reset the workflow."
- Optionally ask for an archive summary message
Step 3: Execute Archive
Before archiving, call openspec_get_pending_hooks({ hookPoint: "pre_archive" }).
Required hooks must be recorded as passed or skipped with openspec_record_hook_result.
Before calling openspec_archive_change, call openspec_sync_specs for the relevant
domain names so the change delta is appended to openspec/specs/<domain>/spec.md.
If the domain is unknown, use general. Then call docs_check_freshness; unresolved
stale domain specs should block archive unless the user explicitly accepts the gap.
Call openspec_archive_change with an optional summary message:
openspec_archive_change({
message: "Implemented X feature with Y approach. Key decisions: ..."
})
This:
- Copies active artifacts to
openspec/changes/archive/<changeId>/ - Writes
archive-metadata.jsonwith timestamps and paths - Adds an entry to
openspec/changes/archive/_knowledge-base/<changeId>.jsonfor the accumulated knowledge base - Preserves the main domain spec sync metadata in state
- Resets the state machine to
completephase
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 · 98 lines · 33 tokens per session scan A 27eed9f965e0
codex-sdd:archive is a skill published in the GitHub repository skyloevil/codex-sdd (1 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session and 816 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
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.