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 commands/koolamusic/claudefiles/archivegit clone --depth 1 https://github.com/koolamusic/claudefilesWrote 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/commands/koolamusic/claudefiles/archive)<a href="https://agentmods.dev/commands/koolamusic/claudefiles/archive"><img src="https://agentmods.dev/badge/commands/koolamusic/claudefiles/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.00050 | $0.01087 |
| Opus 5 | $0.00025 | $0.00544 |
| Sonnet 5 | $0.00010 | $0.00217 |
| Haiku 4.5 | $0.00005 | $0.00109 |
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 4d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/studio:archive
For projects that are completed or wound down. The workspace moves out of the
~/.studio/ root into ~/.studio/_archive/<slug>/ — a fixed convention, like
.workspacerc and _index.md, not a studio.yaml value — so the store root
lists only active work. Git history preserves everything; nothing is deleted.
Archiving is a store-side move plus a machine-local cleanup. Other machines with checkouts of the same project clean themselves up on their next session (their session-start hook fails to resolve the workspace and points here).
Steps
-
Resolve slug. If
$ARGUMENTSnames a slug, use it. Otherwise rungit rev-parse --show-topleveland read$PROJECT_ROOT/.workspacerc— theworkspacefield's basename is the slug. If neither yields a slug, stop and ask. -
Verify the workspace. Confirm
~/.studio/.gitexists, then branch on where the slug lives:~/.studio/$SLUGexists,_archive/$SLUGdoes not — normal case; continue with step 3.~/.studio/$SLUGdoes not exist but_archive/$SLUGdoes — already archived (another machine or collaborator did the store-side move, e.g. after agit pullin~/.studio). Skip steps 3–5 and jump straight to step 6: this machine only needs its local cleanup. Say so in the report.- Both exist — STOP. A previous archive of the same slug is in place and
a live workspace has reappeared beside it; never overwrite. Surface via
AskUserQuestion(suffix the new archive, or cancel). - Neither exists — STOP; nothing to archive under that slug.
-
Confirm intent. Archiving is meant for completed work. Use
AskUserQuestionto confirm: show the slug, its last workspace commit touching it (cd ~/.studio && git log -1 --format='%h %ad %s' --date=short -- $SLUG/), and proceed/cancel. Skip the question only if the user's invocation already named the slug explicitly. -
Move. In
~/.studio:mkdir -p _archive && git mv "$SLUG" "_archive/$SLUG".git mvonly carries tracked files — afterwards check[[ -e "$SLUG" ]]for untracked leftovers; if any remain,mvthem into_archive/$SLUG/preserving relative paths, then remove the empty source dir.
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.
- 4d ago First seen · 79 lines · 50 tokens per session scan A 82c4c2e20801
archive is a command published in the GitHub repository koolamusic/claudefiles (132 stars, last pushed 4d ago), licensed MIT. It adds 50 tokens to every session and 1,087 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-30.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.