archive-intermediate

A procedure for documenting a completed intermediate feature in a project archive. It collects the feature’s plan, design notes, implementation details, reflection, and related commits in one record.

In plain words
What is it for?
Use it to check that reflection is complete, gather feature documents, record affected files, and link the final code changes. It is intended for significant features that span several parts of a project.
Why use it?
It prevents the reasoning and lessons behind a feature from being lost after the work is finished. It also makes past decisions easier to find later.

Cursor rule for Cursor

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 rules/alkoleft/platform-context-exporter/archive-intermediate
Clone the repo
git clone --depth 1 https://github.com/alkoleft/platform-context-exporter

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 1,135 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod 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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.01135
Opus 5 $0.00000 $0.00567
Sonnet 5 $0.00000 $0.00227
Haiku 4.5 $0.00000 $0.00113

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

Security

Grade A, and why

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

Origin

This is a copy

100% identical to archive-intermediate — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.cursor/rules/isolation_rules/Level3/archive-intermediate.mdc · 79 lines

How it starts

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

LEVEL 3 ARCHIVE: INTERMEDIATE FEATURE DOCUMENTATION

TL;DR: This guide outlines the archiving process for a completed Level 3 intermediate feature. The aim is to create a self-contained, easily accessible record of the feature's development lifecycle, including its planning, design decisions, implementation summary, and reflection.

🚀 Before You Start Archiving (L3 Pre-Archive Checklist)

  1. Confirm Reflection Complete: Verify in memory-bank/tasks.md that the reflection phase for this feature is marked as complete and memory-bank/reflection-[feature_id].md exists and is finalized.
  2. Gather All Feature-Specific Documents:
    • The feature plan section from memory-bank/tasks.md (or a copy of it).
    • All memory-bank/creative/creative-[aspect_name].md documents related to this feature.
    • The memory-bank/reflection/reflection-[feature_id].md document.
    • Key diagrams or architectural notes from memory-bank/progress.md if not captured elsewhere.
    • A link to the primary commit(s) or feature branch merge for the implemented code.

📦 Level 3 Archiving Workflow

graph TD
    StartArchive["Start L3 Archiving"] -->
    VerifyReflect["1. Verify Reflection Complete<br>Check `tasks.md` & `reflection-[feature_id].md`"] -->
    GatherDocs["2. Gather All Feature Documents<br>(Plan, Creative outputs, Reflection, Code links)"] -->
    CreateArchiveFile["3. Create Feature Archive File<br>e.g., `memory-bank/archive/feature-[FeatureNameOrID]_YYYYMMDD.md`"] -->
    PopulateArchive["4. Populate Archive File<br>(Using L3 Archive Template below)"] -->
    VerifyLinks["5. Verify All Internal Links<br>in Archive File are Correct"] -->
    FinalUpdateTasks["6. Final Update to `tasks.md`<br>(Mark Feature FULLY COMPLETED & ARCHIVED, link to archive file)"] -->
    UpdateProgressFile["7. Add Final Entry to `progress.md`<br>(Note archiving & link to archive file)"] -->
    ClearActiveCtx["8. Clear `activeContext.md`<br>Reset for Next Task/Project"] -->
    ArchiveDone["L3 Archiving Complete<br>Feature successfully documented and closed."]

    style StartArchive fill:#90a4ae,stroke:#607d8b
    style ArchiveDone fill:#b0bec5,stroke:#90a4ae

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

  1. 3d ago First seen · 79 lines · 0 tokens per session scan A 47b123e9b310

Subscribe to this mod's changes

archive-intermediate is a cursor rule published in the GitHub repository alkoleft/platform-context-exporter (48 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,135 tokens. A static security scan graded it A with 0 findings. It is 100% identical to archive-intermediate, differing in 0 lines, and is treated as a copy.