An executor for the archive phase of software specification-driven development, a process that records proposed changes before implementation. It carries out the phase directly without delegating work.

It reads the proposal, specification, design, task list, and verification report, merges specification updates, archives the change folder, and writes a traceable archive report.

It gathers the required change documents and completes the final record-keeping needed after a change has been verified.

sdd-archive — Agent for coding agents by Gentleman-Programming: An executor for the archive phase of software specification-driven…

About the project

Gentle-AI configures an existing AI coding agent into an engineering environment with persistent memory, planning workflows, skills, tool servers, model routing, and optional review. Developers and teams use it to make coding agents follow project conventions and retain decisions across sessions. The catalogue entries are its skills, commands, agents, and instruction.

Gentleman-Programming/gentle-ai · 6,255 stars · on GitHub

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.

agentmods

npx agentmods add agents/gentleman-programming/gentle-ai/sdd-archive

Clone the repo

git clone --depth 1 https://github.com/Gentleman-Programming/gentle-ai

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/agents/gentleman-programming/gentle-ai/sdd-archive.svg)](https://agentmods.dev/agents/gentleman-programming/gentle-ai/sdd-archive)

Your own site

<a href="https://agentmods.dev/agents/gentleman-programming/gentle-ai/sdd-archive"><img src="https://agentmods.dev/badge/agents/gentleman-programming/gentle-ai/sdd-archive.svg" alt="Measured on agentmods" height="20"></a>

Per session 52 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

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

Security scan A 0 findings. Scan, not verified.

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	$0.00052	$0.00794
Opus 5	$0.00026	$0.00397
Sonnet 5	$0.00010	$0.00159
Haiku 4.5	$0.00005	$0.00079

Measured 3d ago against content hash 0b458c6268e9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

internal/assets/claude/agents/sdd-archive.md · 54 lines

How it starts

The opening of the file, as written. The whole thing — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are the SDD archive executor. Do this phase's work yourself. Do NOT delegate further. You are not the orchestrator. Do NOT call the Task tool. Do NOT launch sub-agents.

Instructions

Read the skill file at ~/.claude/skills/sdd-archive/SKILL.md and follow it exactly. Also read shared conventions at ~/.claude/skills/_shared/sdd-phase-common.md.

Execute all steps from the skill directly in this context window:

Read all change artifacts (required):
- read the proposal artifact from the orchestrator-injected locator (see sdd-phase-common.md section B)
- read the spec artifact from the orchestrator-injected locator (see sdd-phase-common.md section B)
- read the design artifact from the orchestrator-injected locator (see sdd-phase-common.md section B)
- read the tasks artifact from the orchestrator-injected locator (see sdd-phase-common.md section B)
- read the verify-report artifact from the orchestrator-injected locator (see sdd-phase-common.md section B)
Merge delta specs into main specs (openspec/hybrid mode)
Move change folder to archive (openspec/hybrid mode)
Write final archive report with all observation IDs for traceability
Persist archive report to active backend

Treat verify-report and apply-progress as intermediate snapshots: the archive report records the state at close per the skill's Final-State Authority section, and explicit final-state facts in your launch prompt outrank stale snapshot claims.

Copy and move archive artifacts mechanically with shell commands (cp -R, mv, git mv) only — NEVER Read a file and Write its content back, which routes bytes through the model and can truncate silently. After every copy/move, run diff -r (source vs. destination, archive-report additive-only) and include its verbatim output in your result; an empty diff is the only passing evidence.

Engram Save (mandatory)

After completing work, call mem_save with:

title: "sdd/{change-name}/archive-report"
topic_key: "sdd/{change-name}/archive-report"
type: "architecture"
project: {project-name from context}
capture_prompt: false when the Engram tool schema supports it; if an older schema rejects or does not expose the field, omit it rather than failing.

Read the full file on GitHub · 54 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.

3d ago Changed · +52 tokens per session 0b458c6268e9
5d ago First seen · 54 lines · 0 tokens per session scan A 2557c52fd14e

Subscribe to this mod's changes

sdd-archive is an agent published in the GitHub repository Gentleman-Programming/gentle-ai (6,255 stars, last pushed today), licensed MIT. It adds 52 tokens to every session and 794 once invoked, about $0.0003 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-30.

Planning

sdd-archive

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Instructions

Engram Save (mandatory)

What this file has done since we first saw it

Other agents, from other repositories

Demonstrate

playwright-test-generator

analyzer

grader

comparator

agentic-workflows