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/ssbun/csl-agent-kit/archivenpx skills add SSBun/csl-agent-kit --skill archivegit clone --depth 1 https://github.com/SSBun/csl-agent-kitWrote 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/ssbun/csl-agent-kit/archive)<a href="https://agentmods.dev/skills/ssbun/csl-agent-kit/archive"><img src="https://agentmods.dev/badge/skills/ssbun/csl-agent-kit/archive.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 | $0.00060 | $0.00647 |
| Opus 5 | $0.00030 | $0.00324 |
| Sonnet 5 | $0.00012 | $0.00129 |
| Haiku 4.5 | $0.00006 | $0.00065 |
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 3d 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Archive Conversation
Save a verbatim historical transcript from the current Pi session. The command argument is a selection instruction, never transcript content.
Workflow
-
Require a non-empty selection instruction; ask what to preserve when missing.
-
Resolve the source boundary:
- For
/archive, use the host-provided session file, workspace, and source leaf. - For natural Pi invocation, use
PI_SESSION_FILE, list the active branch, and exclude the current archive request. - Without a raw Pi session file or reliable endpoint, stop rather than reconstructing from memory or compacted context.
- For
-
Inspect visible messages:
node <skill-dir>/scripts/archive-session.mjs list --session <session-file> [--leaf <source-leaf>] [--limit 200]Increase the limit only when the requested segment is older.
-
Map the instruction to one contiguous inclusive message-ID range. A topic is sufficient only when it identifies one clear segment. If multiple ranges or endpoints are plausible, ask one focused clarification before writing.
-
Inspect exact candidate text when needed:
node <skill-dir>/scripts/archive-session.mjs show --session <session-file> [--leaf <source-leaf>] --from <message-id> --to <message-id> -
Derive a short title in the user's language and save:
node <skill-dir>/scripts/archive-session.mjs save --session <session-file> [--leaf <source-leaf>] --workspace <workspace> --from <message-id> --to <message-id> --selection <original-instruction> --title <title> -
Report only the saved path and message count.
Exactness Contract
- Preserve selected User and Agent text in branch order without summarizing, correcting, translating, escaping, or normalizing whitespace.
- Include only text blocks from standard
userandassistantmessages. - Exclude system/developer prompts, thinking, tool calls/results, images, custom entries, compaction summaries, and abandoned branches.
- The script owns extraction and writing; never copy transcript text manually.
- Exclude the
/archivedispatch turn unless explicitly requested. - V1 supports one contiguous range. For tool data or disjoint ranges, explain the boundary and ask for one supported range.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 55 lines · 60 tokens per session scan A fe4d4ee745a9
archive is a skill published in the GitHub repository SSBun/csl-agent-kit (10 stars, last pushed 5d ago), licensed MIT. It adds 60 tokens to every session and 647 once invoked, about $0.0003 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…