A procedure for closing a completed change or effort by moving its project folder into context/archive/ and recording when it was archived. An effort is a larger body of work that can contain several changes.

Use it when a change or effort is finished and its folder should be retired. It also identifies open child changes or pending review findings that need attention first.

It keeps finished work separate from active work and prevents incomplete work from being marked done accidentally. It checks child changes and unresolved implementation-review findings before archiving.

dx-archive — Skill for Claude Code by dikamilo/dx-workflow

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 dikamilo/dx-workflow --skill dx-archive

Clone the repo

git clone --depth 1 https://github.com/dikamilo/dx-workflow

Made for: Claude Code.

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/dikamilo/dx-workflow/dx-archive/github.svg)](https://agentmods.dev/skills/dikamilo/dx-workflow/dx-archive)

Your own site

<a href="https://agentmods.dev/skills/dikamilo/dx-workflow/dx-archive"><img src="https://agentmods.dev/badge/skills/dikamilo/dx-workflow/dx-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/dikamilo/dx-workflow/dx-archive"><img src="https://agentmods.dev/badge/skills/dikamilo/dx-workflow/dx-archive.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 665 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.00023	$0.00665
Opus 5.5	$0.00009	$0.00266
Sonnet 5.5	$0.00005	$0.00133
Haiku 4.5	$0.00002	$0.00067

Measured 22d ago against content hash 399b4ebe4f30, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

dx-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 22d 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/dx-archive/SKILL.md · 44 lines

How it starts

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

dx-archive

Retire a finished container. One id in, one folder moved, one stamp written. No registry — the archive is just where done work lives.

Guard. If the id resolves to nothing, or the folder can't move cleanly, do nothing and say why. Never half-move.

Resolve

The argument is one id. Find its home:

context/changes/<id>/ → it's a change.
context/efforts/<id>/ → it's an effort.
Neither, or both → fail loud: print what you looked for and stop. (Already under context/archive/? Say it's already archived.)

Effort gate — children first

An effort is done only when every child change is already archived. Before moving an effort, read its roadmap.md, and for each linked child change check for archived_at (derive it — scan the child's change.md, don't trust a checkbox). If any child is still open, list them and ask before continuing. The user may override.

Review gate — unresolved findings

Scan every reviews/*.md in the container except the legacy impl-review.md and plan-review.md, which triage no longer reads. For each report with any finding marked Resolution: PENDING, warn — "N unresolved finding(s) in reviews/.md — /dx-review-triage to address them first" — and ask whether to archive anyway. The user may override.

Move and stamp

Destination: context/archive/<today>-<id>/ where <today> is date +%F. If it already exists, fail loud and stop.
Stamp the moved container's change.md (or effort.md): set status: archived and archived_at: to today's date (date +%F, same format as created/updated — no other field in the schema carries a finer timestamp); bump updated:. Leave every other field alone. For the exact schema, invoke dx-references with topic change-md (a change) or effort-md (an effort).
Move the whole folder: prefer git mv so history follows; fall back to mv (warn) if git is unavailable. Confirm the source is gone and the destination exists — if not, print a diagnostic and stop.

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

22d ago Changed 399b4ebe4f30
1mo ago Changed · -1 lines 22fec0b00d8e
2mo ago First seen · 45 lines · 23 tokens per session scan A 854840be8562

Subscribe to this mod's changes

dx-archive is a skill published in the GitHub repository dikamilo/dx-workflow (8 stars, last pushed 23d ago), licensed MIT. It adds 23 tokens to every session and 665 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.

Claude Code Project management skills

antfu-issue-triage

Triage open issues and PRs of the current GitHub repo - find already-fixed, duplicate, and spam items, suggest labels, gauge demand from reactions and comments, then present a table of proposed actions and comments for confirmation before touching anything. Use when asked to triage, organize, clean up, or groom issues…

antfu/skills · 76 tokens

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

dx-archive

Resolve

Effort gate — children first

Review gate — unresolved findings

Move and stamp

What this file has done since we first saw it

Other skills, from other repositories

antfu-issue-triage

to-spec

factory-collect

factory-human-digest

factory

factory-recover