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.
npx agentmods add skills/zate/cc-plugins/archivenpx skills add Zate/cc-plugins --skill archivegit clone --depth 1 https://github.com/Zate/cc-pluginsWhat 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 | $0.00012 | $0.00746 |
| Opus 5 | $0.00006 | $0.00373 |
| Sonnet 5 | $0.00002 | $0.00149 |
| Haiku 4.5 | $0.00001 | $0.00075 |
Grade A, and why
archive 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.
How it starts
The opening of the file, as written. The whole thing — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Archive - Move Completed Plan to Archive
Archive a completed plan to .devloop/archive/ and clear the active plan. You do the work directly.
Step 1: Check Plan Status
"${CLAUDE_PLUGIN_ROOT}/scripts/check-plan-complete.sh" .devloop/plan.md
Parse the JSON output to get task counts.
If no plan exists:
No active plan to archive.
Run /devloop or /devloop:plan to create a new plan.
If plan has pending tasks: Show status and ask:
AskUserQuestion:
questions:
- question: "Plan has N pending tasks. Archive anyway?"
header: "Incomplete"
multiSelect: false
options:
- label: "Archive anyway"
description: "Force archive incomplete plan"
- label: "Continue work"
description: "Keep working on pending tasks"
- label: "Cancel"
description: "Don't archive"
Step 2: Show What Will Be Archived
Use the Read tool with limit: 20 on .devloop/plan.md to show the plan header.
Display:
Plan to archive:
Title: [Plan title]
Tasks: N completed / M total
Created: [date]
Archive destination: .devloop/archive/YYYY-MM-DD-{slug}.md
Step 3: Confirm or Auto-Archive
If plan is complete: Skip confirmation — execute archive directly.
If plan is incomplete (user chose "Archive anyway" in Step 1): Execute archive with --force.
If --force argument: Skip confirmation — execute archive directly.
Otherwise: Ask:
AskUserQuestion:
questions:
- question: "Archive this plan?"
header: "Confirm"
multiSelect: false
options:
- label: "Archive now"
description: "Move plan to archive, clear active plan"
- label: "Cancel"
description: "Keep plan active"
Step 4: Execute Archive
If confirmed (or auto-archiving complete plan, or --force):
"${CLAUDE_PLUGIN_ROOT}/scripts/archive-plan.sh" .devloop/plan.md
If user selected "Archive anyway" for incomplete plan:
"${CLAUDE_PLUGIN_ROOT}/scripts/archive-plan.sh" .devloop/plan.md --force
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.
- 2d ago First seen · 127 lines · 12 tokens per session scan A a3fca9a16d06
archive is a skill published in the GitHub repository Zate/cc-plugins (10 stars, last pushed 1mo ago), licensed MIT. It adds 12 tokens to every session and 746 once invoked, about $0.0001 per session on Opus 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…