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/nvk/llm-wiki/archivegit clone --depth 1 https://github.com/nvk/llm-wikiWhat 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.00036 | $0.01576 |
| Opus 5 | $0.00018 | $0.00788 |
| Sonnet 5 | $0.00007 | $0.00315 |
| Haiku 4.5 | $0.00004 | $0.00158 |
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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Your task
Manage the archive lifecycle for topic wikis. Archive is a context filter, not deletion: preserve the wiki, remove it from normal semantic workflows, and keep explicit restore/maintenance possible.
Read skills/wiki-manager/references/archive.md,
skills/wiki-manager/references/hub-resolution.md, and
skills/wiki-manager/references/wiki-structure.md before mutating files.
Resolve HUB
Archive is a hub-level operation. Resolve HUB with the standard protocol:
- Read
$HOME/.config/llm-wiki/config.json. Preferhub_path, expanding only a leading~. Useresolved_pathonly as the legacy fallback described inhub-resolution.md. - If no config exists, try
$HOME/wiki/_index.md. - Verify
HUB/wikis.jsonandHUB/topics/exist, unless the subcommand is helping initialize/report an empty hub. - If the path can be statted but reading
wikis.jsonor listingtopics/fails withOperation not permitted, stop with the hub-resolution diagnostic and do not fall back to another path.
Do not archive project-local .wiki/ directories in v1. Project archive remains
/wiki:project archive; inventory and dataset archive remain status: archived.
Parse $ARGUMENTS
Subcommands:
- list: show active topic wikis and archived counts. With
--archived, show archived topics in a separate table. - topic : archive an active topic wiki.
- restore : restore an archived topic wiki to active status.
- peek : search archived topic indexes only and report possible matches without reading archived articles.
Flags:
- --reason "why": optional archive reason stored in
wikis.json. - --archived: include archived topics in list output.
- --include-archived: allow explicit archived reads for
peekor when a routed query follows an archived match.
If the input is empty, show the subcommands and examples.
Archive Topic
For topic <slug>:
- Refuse
slug = hub. - Read
HUB/wikis.json. - Resolve the active topic path:
- Prefer a registry entry whose
statusis notarchived. - Resolve registry paths as
<HUB>,~, absolute, or HUB-relative. - If the registry is stale but
HUB/topics/<slug>/_index.mdexists, use it and repair the registry.
- Prefer a registry entry whose
- Fail if the source wiki is missing or already archived.
- Fail if
HUB/topics/.archive/<slug>/already exists. mkdir -p HUB/topics/.archive- Move
HUB/topics/<slug>toHUB/topics/.archive/<slug>. - Update
wikis.json:path: "topics/.archive/<slug>"status: "archived"archived: YYYY-MM-DDarchive_reason: "<reason>"when provided
- Regenerate the hub
_index.mdactive-topic table so archived topics do not appear as active. Include an archived count. - Append logs:
HUB/log.md:## [YYYY-MM-DD] archive | archived topic <slug>- archived topic
log.md: same entry, if writable.
- Report the old path, new path, and restore command.
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 · 159 lines · 36 tokens per session scan A c6255bd32800
archive is a command published in the GitHub repository nvk/llm-wiki (1,175 stars, last pushed 6d ago), licensed MIT. It adds 36 tokens to every session and 1,576 once invoked, about $0.0002 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
implement
Execute phased implementation with validation gates.
loop
Iteratively fix issues until all resolved or max iterations reached.
project
Generate project documentation (product.md, structure.md, tech.md, codemaps/).
review
Code review with security and @MX tag compliance check.
status
Show current Craft progress — cycles, stories, backlog in a rich dashboard view.
story-implement-auto
Autonomous story implementation — auto-picks stories, chains through cycle, no interactive prompts.