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/datasetgit 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.00030 | $0.02358 |
| Opus 5 | $0.00015 | $0.01179 |
| Sonnet 5 | $0.00006 | $0.00472 |
| Haiku 4.5 | $0.00003 | $0.00236 |
Grade A, and why
dataset 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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Your task
Resolve the wiki. Do NOT broadly search the filesystem — 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 → stop with "No wiki found. Run/wiki initfirst."
Archive rule: dataset commands operate on active topic wikis by default. If a
named target is archived, stop and ask the user to restore it or rerun with
--include-archived. When explicitly included, list/update manifests only
inside that archived topic path and label the result as archived. This is
separate from dataset manifest status: archived.
After resolving the wiki, read the dataset reference at skills/wiki-manager/references/datasets.md, then run the requested subcommand.
Dataset manifests are for large or external data that should not be copied into
raw/ or wiki/. The wiki stores pointers, schema notes, small samples,
profiles, query recipes, and provenance. Actual datasets remain at their
original filesystem path, object store, URL, database, or archive.
Be opinionated about whether a dataset manifest is warranted:
- Good fit: large, mutable, remote, compressed, binary, database-backed, or query-oriented data that should stay outside markdown.
- Too small: a short CSV/JSON/text file that can be ingested as one immutable
raw/data/source. - Too operational: a next-action queue about a corpus belongs in inventory, with an optional link to a dataset manifest.
- Too broad: many independent sources/pages should usually be
ingest-collection, not a dataset manifest.
Before larger pivots, preview the shape: one dataset manifest plus any linked inventory record, sample/profile/query notes, and what data will remain external. Do not ask the user to approve a big migration without showing this sample.
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 · 176 lines · 30 tokens per session scan A 845b1ba15151
dataset is a command published in the GitHub repository nvk/llm-wiki (1,175 stars, last pushed 6d ago), licensed MIT. It adds 30 tokens to every session and 2,358 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
cost-analyze
Analyze and optimize LLM API costs with 2026 pricing.
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/).
status
Show current Craft progress — cycles, stories, backlog in a rich dashboard view.
ask
Consult a craft agent. Routes your question to the best mind in the workshop - not a menu, a recommendation.