archive-basic

archive-basic is a cursor rule for Cursor from bia-technologies/yaxunit. It costs 1,153 tokens per session, scanned A, original, Apache-2.0.

A short archive format for recording what a completed enhancement changed, when it was completed, which files were modified, and how it was tested.

In plain words
What is it for?
It is for documenting completed enhancements, their requirements, implementation details, tests, and links to related work.
Why use it?
It preserves useful project history and makes past changes easier to understand and find later.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is - [X] [Feature Name] (YYYY-MM-DD) - [Archive Link](../docs/archive/enhancements/YYYY-MM/feature-name.md).

Good fit It is for documenting completed enhancements, their requirements, implementation details, tests, and links to related work.

Compare 6 cursor rules from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/bia-technologies/yaxunit
agentmods
npx agentmods add rules/bia-technologies/yaxunit/archive-basic

Made for: Cursor.

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.

agentmods badge for archive-basic

README.md
[![agentmods](https://agentmods.dev/badge/rules/bia-technologies/yaxunit/archive-basic/github.svg)](https://agentmods.dev/rules/bia-technologies/yaxunit/archive-basic)
Your own site
<a href="https://agentmods.dev/rules/bia-technologies/yaxunit/archive-basic"><img src="https://agentmods.dev/badge/rules/bia-technologies/yaxunit/archive-basic/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.

agentmods 80×15 button for archive-basic

Your own site · 80×15
<a href="https://agentmods.dev/rules/bia-technologies/yaxunit/archive-basic"><img src="https://agentmods.dev/badge/rules/bia-technologies/yaxunit/archive-basic.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,153 This file is loaded in full into every session.
When invoked 1,153 The same file — it is already loaded in full.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.01153 $0.01153
Opus 5.5 $0.00461 $0.00461
Sonnet 5.5 $0.00231 $0.00231
Haiku 4.5 $0.00115 $0.00115

Measured 1mo ago against content hash 2e4bfff7fbf2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 1mo 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

Copies of this mod

3 near-identical copies found in the catalogue:

.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. 1mo 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 bia-technologies/yaxunit (339 stars, last pushed 9d ago), licensed Apache-2.0. It adds 1,153 tokens to every session, about $0.0046 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-09-01.