archive-basic

A lightweight process for documenting completed Level 2 software enhancements and preserving what changed, why it changed, and how it was tested.

In plain words
What is it for?
Use it to create brief archives containing the enhancement summary, completion date, changed files, requirements, implementation notes, tests, and related references.
Why use it?
It prevents small completed tasks from losing their context or becoming difficult 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/mcp-bsl-platform-context/archive-basic
Clone the repo
git clone --depth 1 https://github.com/alkoleft/mcp-bsl-platform-context

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 1,153 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.01153
Opus 5 $0.00000 $0.00576
Sonnet 5 $0.00000 $0.00231
Haiku 4.5 $0.00000 $0.00115

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

Security

Grade A, and why

archive-basic 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 2d 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-basic — 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/Level2/archive-basic.mdc · 181 lines

How it starts

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

BASIC ARCHIVING FOR LEVEL 2 TASKS

TL;DR: This document outlines a basic archiving approach for Level 2 (Simple Enhancement) tasks, ensuring that completed work is properly documented and knowledge is preserved with minimal overhead.

🔍 ARCHIVING OVERVIEW

Even for Level 2 tasks, proper archiving ensures that completed work is documented and knowledge is preserved. This basic archiving approach provides sufficient structure while maintaining efficiency.

📋 ARCHIVING PRINCIPLES

  1. Completion: Clearly document what was completed
  2. Context: Preserve the context of the enhancement
  3. Knowledge: Capture key insights and lessons
  4. Findability: Make archived information easy to find
  5. References: Create cross-references to related work

📋 BASIC ARCHIVE STRUCTURE

# Enhancement Archive: [Feature Name]

## Summary
[Brief summary of the enhancement]

## Date Completed
YYYY-MM-DD

## Key Files Modified
- [File path 1]
- [File path 2]
- [File path 3]

## Requirements Addressed
- [Requirement 1]
- [Requirement 2]
- [Requirement 3]

## Implementation Details
[Brief description of how the enhancement was implemented]

## Testing Performed
- [Test 1]
- [Test 2]
- [Test 3]

## Lessons Learned
- [Lesson 1]
- [Lesson 2]
- [Lesson 3]

## Related Work
- [Link to related task/enhancement 1]
- [Link to related task/enhancement 2]

## Notes
[Any additional information or context]

📋 ARCHIVE LOCATION

Store archives in an organized structure:

docs/
└── archive/
    └── enhancements/
        └── YYYY-MM/
            ├── feature-name-1.md
            └── feature-name-2.md

📋 ARCHIVING PROCESS

Follow these steps to archive a Level 2 task:

  1. Prepare Archive Content:

    • Gather all relevant information
    • Fill in the archive template
    • Include all key implementation details
  2. Cross-Reference Creation:

    • Update tasks.md with link to archive
    • Add reference in progress.md
    • Update activeContext.md with next focus

Read the full file on GitHub · 181 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. 2d ago First seen · 181 lines · 1,153 tokens per session scan A 2e4bfff7fbf2

Subscribe to this mod's changes

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