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.
git clone --depth 1 https://github.com/alkoleft/platform-context-exporterWrote 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.
[](https://agentmods.dev/rules/alkoleft/platform-context-exporter/archive-comprehensive)<a href="https://agentmods.dev/rules/alkoleft/platform-context-exporter/archive-comprehensive"><img src="https://agentmods.dev/badge/rules/alkoleft/platform-context-exporter/archive-comprehensive.svg" alt="Measured on agentmods" height="20"></a>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.04869 | $0.04869 |
| Opus 5 | $0.02434 | $0.02434 |
| Sonnet 5 | $0.00974 | $0.00974 |
| Haiku 4.5 | $0.00487 | $0.00487 |
Grade A, and why
archive-comprehensive 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 7d 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.
This is a copy
100% identical to archive-comprehensive — 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.
How it starts
The opening of the file, as written. The whole thing — 685 lines — stays where its author put it; the contents beside it link to each section on GitHub.
COMPREHENSIVE ARCHIVING FOR LEVEL 4 TASKS
TL;DR: This document outlines a comprehensive archiving approach for Level 4 (Complex System) tasks, ensuring all system knowledge, decisions, implementation details, and lessons learned are preserved for future reference and reuse.
🔍 COMPREHENSIVE ARCHIVING OVERVIEW
Level 4 Complex System tasks require thorough archiving to preserve system knowledge, design decisions, implementation details, and lessons learned. This systematic archiving process ensures that the organization maintains institutional knowledge and enables future teams to understand, maintain, and extend the system.
flowchart TD
classDef phase fill:#f9d77e,stroke:#d9b95c,color:#000
classDef artifact fill:#f4b8c4,stroke:#d498a4,color:#000
classDef verification fill:#c5e8b7,stroke:#a5c897,color:#000
Start([Begin Archiving<br>Process]) --> Template[Load Comprehensive<br>Archive Template]
Template --> RefDoc[Review Reflection<br>Document]
RefDoc --> SysDoc[Create System<br>Documentation]
SysDoc --> ArchDoc[Document Architecture<br>and Design]
ArchDoc --> ImplDoc[Document Implementation<br>Details]
ImplDoc --> APIDoc[Create API<br>Documentation]
APIDoc --> DataDoc[Document Data<br>Models and Schemas]
DataDoc --> SecDoc[Document Security<br>Measures]
SecDoc --> TestDoc[Document Testing<br>Procedures and Results]
TestDoc --> DeployDoc[Document Deployment<br>Procedures]
DeployDoc --> OpDoc[Create Operational<br>Documentation]
OpDoc --> KnowledgeDoc[Create Knowledge<br>Transfer Documentation]
KnowledgeDoc --> CrossRef[Create Cross-Reference<br>Documentation]
CrossRef --> Archive[Archive All<br>Project Materials]
Archive --> UpdateMB[Update Memory<br>Bank]
UpdateMB --> Verification{Archiving<br>Verification}
Verification -->|Pass| Complete([Archiving<br>Complete])
Verification -->|Fail| Revise[Revise<br>Archiving]
Revise --> Verification
Template -.-> AT((Archive<br>Template))
SysDoc -.-> SD((System<br>Documentation))
ArchDoc -.-> AD((Architecture<br>Documentation))
ImplDoc -.-> ID((Implementation<br>Documentation))
APIDoc & DataDoc -.-> IntDoc((Interface<br>Documentation))
TestDoc & DeployDoc & OpDoc -.-> OpDocs((Operational<br>Documentation))
class Start,Complete milestone
class Template,RefDoc,SysDoc,ArchDoc,ImplDoc,APIDoc,DataDoc,SecDoc,TestDoc,DeployDoc,OpDoc,KnowledgeDoc,CrossRef,Archive,UpdateMB step
class Verification verification
class AT,SD,AD,ID,IntDoc,OpDocs artifact
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.
- 7d ago First seen · 685 lines · 4,869 tokens per session scan A 4e143af97255
archive-comprehensive is a cursor rule published in the GitHub repository alkoleft/platform-context-exporter (48 stars, last pushed 1y ago), licensed MIT. It adds 4,869 tokens to every session, about $0.0243 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to archive-comprehensive, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
bsl-ssl
A set of rules for developing 1C applications built on БСП, the Russian-language Standard Subsystems Library. It tells developers when to reuse library functionality, how to mark changes, and how to handle outdated objects.
edt-form-xml-requirements
A set of rules for XML form files used by EDT, a development environment for 1C business applications. It describes form details that the code generator does not add automatically.
1c-mdo-integrity
Rules for keeping 1C EDT MDO files structurally valid. MDO files describe configuration objects, and the rules cover unique identifiers and valid links between objects.
1c-report-direct-query
A 1C reporting rule that runs the report query directly instead of using the standard data-composition engine (СКД). It then displays or exports the returned table manually.
1c-skd-two-pass-preprocessing
A two-pass method for changing 1C report output before detailed records are combined into grouped totals. 1C's report system, СКД, builds reports by grouping and summarizing data.
1c-transactions-and-locks
Guidance for using transactions and controlled locks in 1C, where a transaction groups database changes so they can be accepted or cancelled together. It also explains the order in which locks should be taken when several operations share data.