Borrowing it
Nothing to install: this file belongs to hlalljie/agent-workflow-presets. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/hlalljie/agent-workflow-presets/main/.cursor/skills/archive-plan/SKILL.mdgit clone --depth 1 https://github.com/hlalljie/agent-workflow-presetsWrote 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/skills/hlalljie/agent-workflow-presets/archive-plan)<a href="https://agentmods.dev/skills/hlalljie/agent-workflow-presets/archive-plan"><img src="https://agentmods.dev/badge/skills/hlalljie/agent-workflow-presets/archive-plan/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.
<a href="https://agentmods.dev/skills/hlalljie/agent-workflow-presets/archive-plan"><img src="https://agentmods.dev/badge/skills/hlalljie/agent-workflow-presets/archive-plan.svg" alt="Reviewed on agentmods" width="80" 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.00059 | $0.01210 |
| Opus 5.5 | $0.00024 | $0.00484 |
| Sonnet 5.5 | $0.00012 | $0.00242 |
| Haiku 4.5 | $0.00006 | $0.00121 |
Grade A, and why
archive-plan 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 19d 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.
How it starts
The opening of the file, as written. The whole thing — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Archive plan
Where plans live
- Active:
.cursor/plans/<plan-name>/ - Archived:
.cursor/plans-archive/<plan-name>/
The whole folder moves, with the same name and contents, so links inside the plan (tasks to plan.md, plan to research/) keep working. Location is the only state: there is no index and no status field. Moving a plan by hand in either direction is always valid.
When to use
- The commit skill finishes a plan's last phase and hands off here.
- The user asks to archive or restore a plan.
Archive
- Pick the plan. Use the plan the user or the commit skill named. If none was named, list the plans in
.cursor/plans/whose phases are all complete and ask which. - Check it is complete. Every
## Phase N:heading inplan.mdends— complete, and the Backlog section is empty or absent. If not, list the open phases and stop, unless the user asked to archive it anyway. - Check the target. If
.cursor/plans-archive/<plan-name>/already exists, stop and ask for a different name. Never overwrite or merge. - Find references. Search the repo, excluding
.git/and the plan's own folder, forplans/<plan-name>, matching the whole name (foomust not matchfoo-bar). Also search the other plans for relative links to it (../<plan-name>/). - Promote what should outlive the plan.
- Decisions. Read the plan's
decisions.md(number it first if it is unnumbered). Any decision that meets the project-decisions rules in workflow.mdc and has no(<plan-name>/D#)line indocs/decisions.mdgets a line there now. Create the file if it does not exist. - Architecture information. Look through
plan.md,research/, and the task files for information about how the system works that is not documented yet: flows, boundaries between parts, contracts, constraints. Skip anything the code or an existing doc already shows. Before writing any of it down, check it is still current against the code anddocs/decisions.md. The plan may predate later decisions or changes, so drop or correct whatever no longer holds, and never let the plan's version override newer decisions. Add what remains to the doc it belongs in, following write-docs and the routing in documentation.mdc:docs/folder-structure.mdfor layout,docs/architecture.mdfor flows, boundaries, contracts, and constraints (create it from the template if it is missing),docs/runbooks/for procedures. If the information fits none of those, list the item in the proposal instead of creating a new kind of doc.
- Decisions. Read the plan's
- Add commit hashes. For each phase whose
Completed:line has only a date (skip phases with no such line), find the commit that added— completeto its heading and append its hash, for exampleCompleted: 2026-10-05, 04ecd2d. Rungit log -S'<full heading line>' --reverse --format=%h -- .cursor/plans/<plan-name>/plan.mdand take the first line of output. If nothing is found (history rewritten, plan copied in from elsewhere), leave the date alone and say so in the proposal. - Move.
- macOS / Linux:
mkdir -p .cursor/plans-archive && mv .cursor/plans/<plan-name> .cursor/plans-archive/<plan-name> - Windows:
New-Item -ItemType Directory -Force .cursor\plans-archive; Move-Item .cursor\plans\<plan-name> .cursor\plans-archive\<plan-name>
- macOS / Linux:
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.
- 19d ago First seen · 41 lines · 59 tokens per session scan A 38c039b03d80
archive-plan is a skill published in the GitHub repository hlalljie/agent-workflow-presets (2 stars, last pushed 20d ago), licensed MIT. It adds 59 tokens to every session and 1,210 once invoked, about $0.0002 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-10-10.
Other skills, from other repositories
work-on-ticket
Fetches Jira ticket details, creates an appropriately named branch, and initiates the task planning workflow. Use when the user says "work on [TICKETID]" or similar phrases.
cast-plan
Turn a request into a plan the team can review before code exists. Explores the codebase, searches prior sessions and recorded decisions for earlier attempts, interviews the user on the open questions, then writes a codecast plan with tasks and dependencies ready for orchestrate. Use when work has several parts, when…
cast-org
Talk through the organization of agents and people around this work with the person, in this session: who reports to whom, what each role looks after, where their sessions go. Reads what the code and the sessions say before it trusts a plan or a task, asks what the records cannot settle, and posts each agreed change…
cast-handoff
Package the current work so the next session or a teammate can continue without reading this thread. Writes the decisions, the direction, what is verified, open questions and ordered next steps as a shared doc, pins the state, and optionally forks, spawns or hands the work to a session. Use before stopping, before a…
cast-loop
Run an autonomous loop that works through a queue of tasks one fresh session at a time, with verification as the gate and a human decision at merge. Sets up a recurring trigger that spawns a session per ready task, a precheck that spends nothing when the queue is empty, and the rules each run follows. Use for a…
cast-conflicts
Before editing or fanning out work, find the live sessions on this repository that are changing the same files, show what they changed, and warn them. Use before starting a task that touches shared files, before spawning workers, or when asked who else is working on this.