What is codex-sdd:archive?

A final step in the OpenSpec workflow, which records a change proposal, design, task list, and related notes in an organised archive.

Archiving validated software changes and updating the project's shared knowledge base.

It keeps completed planning documents available for future reference and marks the workflow as finished.

codex-sdd:archive — Skill for Claude Code and Codex by skyloevil

Install

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.

Any agent

npx skills add skyloevil/codex-sdd --skill archive

Clone the repo

git clone --depth 1 https://github.com/skyloevil/codex-sdd

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/skyloevil/codex-sdd/archive/github.svg)](https://agentmods.dev/skills/skyloevil/codex-sdd/archive)

Your own site

<a href="https://agentmods.dev/skills/skyloevil/codex-sdd/archive"><img src="https://agentmods.dev/badge/skills/skyloevil/codex-sdd/archive/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/skyloevil/codex-sdd/archive"><img src="https://agentmods.dev/badge/skills/skyloevil/codex-sdd/archive.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 816 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00033	$0.00816
Opus 5.5	$0.00013	$0.00326
Sonnet 5.5	$0.00007	$0.00163
Haiku 4.5	$0.00003	$0.00082

Measured 1mo ago against content hash 27eed9f965e0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 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.

skills/archive/SKILL.md · 98 lines

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_status shows phase is validate or archive and 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.md
openspec/changes/<changeId>/tasks.md
openspec/changes/<changeId>/verification.md
openspec/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.json with timestamps and paths
Adds an entry to openspec/changes/archive/_knowledge-base/<changeId>.json for the accumulated knowledge base
Preserves the main domain spec sync metadata in state
Resets the state machine to complete phase

Read the full file on GitHub · 98 lines

Changes

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 · 98 lines · 33 tokens per session scan A 27eed9f965e0

Subscribe to this mod's changes

codex-sdd:archive is a skill published in the GitHub repository skyloevil/codex-sdd (1 stars, last pushed 3mo ago), licensed MIT. It adds 33 tokens to every session and 816 once invoked, about $0.0001 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.

Memory and context OpenSpec Planning agent agentic-workflow codex codex-cli codex-plugin

studio-context-brief

Use when an active KIT-managed Goal needs compact brief, working, or resume context projections from trusted structured state while preserving exact technical literals and durable handoff authority.

hoatv2211/GameStudio-CodexKIT · 37 tokens

handover

Use when wrapping up or capturing the current state of a coding session — writes a short, dated entry to the repo's RepoHandover.md so a future agent or you can resume without grepping archived sessions. Triggers on "handover", "hand off", "write handover", "capture state", "checkpoint this session".

jazzyalex/agent-sessions · 71 tokens

codex-sdd:archive