A command for recording what happened after a task is completed and updating the project's knowledge base for future work.

Summarizing completed work, documenting design choices, capturing lessons learned, updating progress and task files, and identifying patterns worth reusing.

It preserves decisions, deviations, lessons, and reusable patterns instead of letting useful project knowledge disappear after implementation.

archive — Command for Claude Code by d-padmanabhan

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.

Clone the repo

git clone --depth 1 https://github.com/d-padmanabhan/agent-engineering-handbook

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/commands/d-padmanabhan/agent-engineering-handbook/archive/github.svg)](https://agentmods.dev/commands/d-padmanabhan/agent-engineering-handbook/archive)

Your own site

<a href="https://agentmods.dev/commands/d-padmanabhan/agent-engineering-handbook/archive"><img src="https://agentmods.dev/badge/commands/d-padmanabhan/agent-engineering-handbook/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/commands/d-padmanabhan/agent-engineering-handbook/archive"><img src="https://agentmods.dev/badge/commands/d-padmanabhan/agent-engineering-handbook/archive.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 641 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.00011	$0.00641
Opus 5.5	$0.00004	$0.00256
Sonnet 5.5	$0.00002	$0.00128
Haiku 4.5	$0.00001	$0.00064

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

Security

Grade A, and why

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

commands/archive.md · 109 lines

How it starts

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

ARCHIVE MODE ACTIVATED

You are now in ARCHIVE phase.

Purpose

Document the completed task, capture lessons learned, and update the knowledge base for future reference.

When to Use

After /review phase for Level 3-4 tasks
When significant learnings should be preserved
After completing a multi-session task
When patterns emerged that should be documented

Your Tasks

Summarize What Was Done
- What was the original request?
- What was actually implemented?
- Were there any deviations from the plan? Why?
Document Key Decisions
- What design decisions were made?
- What alternatives were considered?
- Why were certain approaches chosen?
Capture Lessons Learned
- What went well?
- What was challenging?
- What would you do differently?
- Any gotchas or surprises?
Update Context Files
- Update tmp/progress.md with completion status
- Create tmp/reflect-<task>.md if significant learnings
- Update tmp/tasks.md to mark task complete
Identify Reusable Patterns
- Any patterns that should be standardized?
- Code that could become a utility?
- Documentation that should be added?

Output Format

## Task Archive: [Task Name]

### Summary
- **Original Request:** [what was asked]
- **Completed:** [date]
- **Duration:** [time spent]
- **Complexity:** Level [1-4]

### What Was Implemented
- [Key change 1]
- [Key change 2]
- [Key change 3]

### Files Changed
- `path/to/file1.py` - [what changed]
- `path/to/file2.py` - [what changed]

### Key Decisions
| Decision | Options Considered | Choice | Rationale |
|----------|-------------------|--------|-----------|
| [Decision 1] | A, B, C | B | [why] |
| [Decision 2] | X, Y | X | [why] |

### Lessons Learned

**What Went Well:**
- [positive 1]
- [positive 2]

**Challenges:**
- [challenge 1] - [how resolved]
- [challenge 2] - [how resolved]

**For Next Time:**
- [improvement 1]
- [improvement 2]

### Reusable Patterns
- [Pattern that could be extracted]
- [Utility that could be created]

### Related Tasks
- [Link to related future work]
- [Technical debt to address]

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

2mo ago First seen · 109 lines · 11 tokens per session scan A 8e3d4bd71053

Subscribe to this mod's changes

archive is a command published in the GitHub repository d-padmanabhan/agent-engineering-handbook (20 stars, last pushed yesterday), licensed MIT. It adds 11 tokens to every session and 641 once invoked, about $0.0000 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-30.

Memory and context

archive next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
archived-padmanabhan/agent-engineering-handbook	Command	20	yesterday	MIT	A	11	Claude Code
minutes-ideassilverstein/minutes	Command	1.6k	yesterday	MIT	A	48	Claude Code, OpenCode
learnReflexioAI/claude-smart	Command	791	3d ago	Apache-2.0	A	14	Claude Code
memory-storeverygoodplugins/mcp-automem	Command	66	yesterday	MIT	A	10	Claude Code
analyze-contextRohiRIK/OpenLtm	Command	29	8d ago	MIT	A	39	Claude Code
cc-memoryTheLobbi/claude	Command	21	7d ago	MIT	A	0	Claude Code
lians-recallLians-ai/Lians	Command	17	5d ago	Apache-2.0	A	19	Claude Code