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/llgit 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.00031 | $0.02398 |
| Opus 5 | $0.00015 | $0.01199 |
| Sonnet 5 | $0.00006 | $0.00480 |
| Haiku 4.5 | $0.00003 | $0.00240 |
Grade A, and why
ll 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.
How it starts
The opening of the file, as written. The whole thing — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Your task
Resolve the wiki. Do NOT search the filesystem or read reference files — follow these steps:
- Read
$HOME/.config/llm-wiki/config.json. If it hashub_path, expand leading~only (not tildes incom~apple~CloudDocs) and prefer that path; useresolved_pathonly as a fallback cache when the expandedhub_pathis unavailable andresolved_pathis initialized. If config has onlyresolved_path, use it. If the configured path can be statted but readingwikis.jsonor listingtopics/fails withOperation not permitted, stop and ask the user to grant Full Disk Access/iCloud Drive access to the launcher; do not fall back to~/wikiorresolved_path. Do not write machine-specificresolved_pathinto shared configs. - If no config → read
$HOME/wiki/_index.md. If it exists → HUB =$HOME/wiki. If nothing found, ask the user where to create the wiki. - Wiki location (first match):
--local→.wiki/in CWD;--wiki <name>→HUB/wikis.jsonlookup with portable path resolution (<HUB>,~, absolute, or HUB-relative); if the registry path is stale, fall back toHUB/topics/<name>; CWD has.wiki/→ use it; else → HUB. - Read
<wiki>/_index.mdto verify. If missing and no wiki matches the session topic → offer to create one with--new-topic; otherwise target the most relevant existing wiki.
Archive rule: lessons learned go to active topic wikis by default. Skip
archived topics when auto-targeting by session topic. If --wiki <name>
resolves to an archived topic, stop and ask the user to restore it or rerun
with --include-archived; explicit archived writes must stay inside the
archived topic path and keep it archived.
Extract lessons learned from the current session and save them to the wiki's knowledge pipeline.
Inventory awareness: if a lesson implies a durable follow-up, recurring watch item, or source/corpus candidate, suggest an inventory record in addition to the raw lesson note. Do not turn every lesson into inventory; only use it when there is status, priority, or a next action to track.
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.
- 2d ago First seen · 227 lines · 31 tokens per session scan A 2f4e540fe3fe
ll is a command published in the GitHub repository nvk/llm-wiki (1,175 stars, last pushed 5d ago), licensed MIT. It adds 31 tokens to every session and 2,398 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
session-memory
Maintain context and learnings across Claude Code sessions for continuous improvement.
implement
Execute phased implementation with validation gates.
workflow-claude-commands
Track Claude Code commands report changes and find what needs updating.
review
Code review with security and @MX tag compliance check.
research-verify
Verify existing research findings against independent primary sources. Upgrades confidence from 'sources agree' to 'independently verified.'.
test-feature
Test a React Native feature on the running simulator/emulator. Verifies UI, user flows, and internal state. Generates a persistent Maestro test file.