assess

assess is a command for coding agents from nvk/llm-wiki. It costs 24 tokens per session (1,848 once invoked), scanned A, original, MIT.

A comparison of a local repository with the active wiki’s research and the wider market. It looks for missing knowledge, opportunities, and competing products or approaches.

In plain words
What is it for?
Use it to assess a repository, find research gaps, explore opportunities, and review the competitive landscape.
Why use it?
It shows where a project may lack research or differ from existing alternatives. That makes gaps and possible directions easier to identify.

Command

Part of the claude-plugin plugin — 1 skill, 28 commands shipped together

Install

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.

agentmods
npx agentmods add commands/nvk/llm-wiki/assess
Clone the repo
git clone --depth 1 https://github.com/nvk/llm-wiki

Or install claude-plugin, the plugin that ships this one along with the rest of its 1 skill, 28 commands.

Wrote 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.

agentmods badge for assess

README.md
[![agentmods](https://agentmods.dev/badge/commands/nvk/llm-wiki/assess.svg)](https://agentmods.dev/commands/nvk/llm-wiki/assess)
Your own site
<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>
Per session 24 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,848 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 4d ago against content hash f61311b30975, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

claude-plugin/commands/assess.md · 163 lines

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:

  1. Read $HOME/.config/llm-wiki/config.json. If it has hub_path, expand leading ~ only (not tildes in com~apple~CloudDocs) and prefer that path; use resolved_path only as a fallback cache when the expanded hub_path is unavailable and resolved_path is initialized. If config has only resolved_path, use it. If the configured path can be statted but reading wikis.json or listing topics/ fails with Operation not permitted, stop and ask the user to grant Full Disk Access/iCloud Drive access to the launcher; do not fall back to ~/wiki or resolved_path. Do not write machine-specific resolved_path into shared configs.
  2. 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.
  3. Wiki location (first match): --local.wiki/ in CWD; --wiki <name>HUB/wikis.json lookup with portable path resolution (<HUB>, ~, absolute, or HUB-relative); if the registry path is stale, fall back to HUB/topics/<name>; CWD has .wiki/ → use it; else → HUB.
  4. Read <wiki>/_index.md to 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:

Read the full file on GitHub · 163 lines

Changes

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.

  1. 4d ago First seen · 163 lines · 24 tokens per session scan A f61311b30975

Subscribe to this mod's changes

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.