archive

A command that moves an accepted task contract from the active folder to an archive folder without deleting it. A task contract is the record of the task and its agreed details.

In plain words
What is it for?
Use /archive with a task ID when the user explicitly wants to store an accepted task. It reports the archive location and does not commit, push, or deploy.
Why use it?
It keeps completed work out of the active task list while preserving a recoverable copy and keeping archiving separate from acceptance.

Command for Claude Code

Install

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.

agentmods
npx agentmods add commands/baek-labs/hames/archive
Clone the repo
git clone --depth 1 https://github.com/baek-labs/hames

Made for: Claude Code.

Per session 18 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 165 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00018 $0.00165
Opus 5 $0.00009 $0.00082
Sonnet 5 $0.00004 $0.00033
Haiku 4.5 $0.00002 $0.00016

Measured 2d ago against content hash 31dfeef4fe7c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

.claude/commands/archive.md · 16 lines

What it actually says

/archive

사용법: /archive <task-id>

작업 계약의 보관은 인수와 별도의 전환이다. 현재 사용자가 이 커맨드를 요청한 때만 실행한다.

node arsenal/task_contract.js archive --workspace "<workspace-path>" --task-id "<task-id>"

helper는 패키지를 .hames/contracts/_Active/에서 같은 워크스페이스의 .hames/contracts/_Archive/로 옮기고 ARCHIVED를 기록한다. 삭제, Git commit/push, 배포를 수행하지 않는다. 완료 보고에는 보관 경로와 복구 가능하다는 점을 포함한다.

Changes

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.

  1. 2d ago First seen · 16 lines · 18 tokens per session scan A 31dfeef4fe7c

Subscribe to this mod's changes

archive is a command published in the GitHub repository baek-labs/hames (5 stars, last pushed 1mo ago), licensed MIT. It adds 18 tokens to every session and 165 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.