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/assessgit clone --depth 1 https://github.com/nvk/llm-wikiWrote 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/nvk/llm-wiki/assess)<a href="https://agentmods.dev/commands/nvk/llm-wiki/assess"><img src="https://agentmods.dev/badge/commands/nvk/llm-wiki/assess.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 | $0.00024 | $0.01848 |
| Opus 5 | $0.00012 | $0.00924 |
| Sonnet 5 | $0.00005 | $0.00370 |
| Haiku 4.5 | $0.00002 | $0.00185 |
Grade A, and why
assess 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 4d 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 — 163 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 → stop with "No wiki found. Run/wiki init <topic>first."
Compare a local repository against the wiki's knowledge base and the broader market. Produce a comprehensive gap analysis.
Inventory awareness: repo/wiki/market gaps that are durable follow-ups should be offered as inventory candidates, especially feature candidates, source queues, competitor watch items, or blocked research tasks. Show a compact sample before creating a larger backlog. Do not use inventory records as evidence in the competitive analysis; cite wiki articles, raw sources, or fresh research.
Deviation: wiki resolution order
Unlike other commands, assess does NOT default to HUB when no wiki is specified — gap analysis against an empty hub is meaningless. The resolution order is:
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.
- 4d ago First seen · 163 lines · 24 tokens per session scan A f61311b30975
assess is a command published in the GitHub repository nvk/llm-wiki (1,188 stars, last pushed 7d ago), licensed MIT. It adds 24 tokens to every session and 1,848 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-30.
Other commands, from other repositories
gen-plan
Generate implementation plan from draft document.
refine-plan
Refine an annotated implementation plan and generate a QA ledger.
gen-idea
Generate a repo-grounded idea draft via directed-swarm exploration.
start-rlcr-loop
Start iterative loop with Codex review.
sync_roleplay_docs
当用户调用此命令时,请同步整理“角色扮演模式(个人扮演模式)”相关的规则、技能、spec 和测试收尾项。.
sync_contributors
当用户调用此命令时,请同步并更新仓库根目录 CONTRIBUTORS.md 以及 README.md 中的贡献者部分,来源为 GitHub 仓库贡献者列表。.