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/kitchen-engineer42/joharnessburg/archivegit clone --depth 1 https://github.com/kitchen-engineer42/joharnessburgWrote 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/kitchen-engineer42/joharnessburg/archive)<a href="https://agentmods.dev/commands/kitchen-engineer42/joharnessburg/archive"><img src="https://agentmods.dev/badge/commands/kitchen-engineer42/joharnessburg/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.1 | $0.00083 | $0.00368 |
| Opus 5 | $0.00042 | $0.00184 |
| Sonnet 5 | $0.00017 | $0.00074 |
| Haiku 4.5 | $0.00008 | $0.00037 |
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 5d 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.
What it actually says
When this command fires:
-
Parse the user's argument. The first positional (if any) is a label for the archive (used in the default filename).
--output <path>overrides the default location.--forceallows overwriting an existing file. -
Invoke the archive script via Bash:
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/archive_workspace.py" <user-args> -
The script returns JSON with
archive_path,file_count, andsize_bytes. Tell the user the zip is ready at the path, with the file count and size. If the user asked for the archive in the context of "we're done", consider also offering to run/john:statusfor a final inventory check before they ship. -
On
success: falsewith "No .john/ directory found", tell the user there's no workspace to archive — they need/john:initfirst.
The archive is suitable for handing to teammates, attaching to a release, or stashing for posterity. It does NOT include .git/, node_modules/, __pycache__/, *.pyc/*.pyo, or .DS_Store — only the durable John artifacts plus the produced skills.
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.
- 5d ago First seen · 21 lines · 83 tokens per session scan A a97044302b68
archive is a command published in the GitHub repository kitchen-engineer42/joharnessburg (9 stars, last pushed 1mo ago), licensed MIT. It adds 83 tokens to every session and 368 once invoked, about $0.0004 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 commands, from other repositories
release
Release manager for frontend and mobile. Writes App Store notes, user-facing changelog, flags stale docs and landing copy. Actions: notes | changelog | docs | sync.
release-check
Pre-release validation pipeline for a component.
commit
Smart conventional commit with security validation, branch flow enforcement, and auto-detection. Use for git commit, commit changes, save work, stage and commit.
release
Generate changelog, bump version, and create git tag.
release
Bump version, commit, push, mirror to ai-skills, and update local plugin.
push
Push direction: ports local mechanism-script fixes back to the hub as a reviewed PR. Opposite of /update.