A command for creating files such as summaries, reports, study guides, slide outlines, timelines, glossaries, and comparisons from wiki content.

Use it to produce structured outputs from an active wiki and save those files back into the wiki.

It turns stored knowledge into formats that are easier to read, study, present, or share.

output — Command for Claude Code by nvk/llm-wiki

About the project

LLM Wiki is a system that uses AI agents to research sources, compile knowledge bases, organize project briefs, and answer questions from the resulting wiki. It is used to turn rough ideas and investigations into structured, reusable knowledge for agents, including Claude Code, Codex, and OpenCode. The catalogue entries are commands, hooks, skills, instructions, and a plugin that implement its workflow.

nvk/llm-wiki · 1,422 stars · on GitHub · llm-wiki.net

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.

Clone the repo

git clone --depth 1 https://github.com/nvk/llm-wiki

Made for: Claude Code.

Or install wiki, 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/nvk/llm-wiki/output/github.svg)](https://agentmods.dev/commands/nvk/llm-wiki/output)

Your own site

<a href="https://agentmods.dev/commands/nvk/llm-wiki/output"><img src="https://agentmods.dev/badge/commands/nvk/llm-wiki/output/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/nvk/llm-wiki/output"><img src="https://agentmods.dev/badge/commands/nvk/llm-wiki/output.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 33 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,730 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00033	$0.01730
Opus 5.5	$0.00013	$0.00692
Sonnet 5.5	$0.00007	$0.00346
Haiku 4.5	$0.00003	$0.00173

Measured 1mo ago against content hash 986a467b7316, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

output 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 1mo 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/output.md · 103 lines

How it starts

The opening of the file, as written. The whole thing — 103 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 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.
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.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.
Read <wiki>/_index.md to verify. If missing → stop with "No wiki found (or no articles). Run /wiki init and /wiki:compile first."

Generate an output artifact from wiki content based on $ARGUMENTS.

Inventory and collect awareness: if the requested output is really a durable queue, candidate list, watch list, source backlog, or next-action table, recommend /wiki:inventory instead of creating another loose output. If the request needs web discovery plus a catalog of artifacts, examples, memes, media, tools, entities, or source candidates, recommend /wiki:collect instead. If an output report discovers durable follow-ups, include a short "Inventory candidates" section with a sample shape and ask before creating records. Do not bury ongoing tracking state in a generated report.

Parse $ARGUMENTS

type (required): One of: summary, report, study-guide, slides, timeline, glossary, comparison. Use /wiki:collect for type: collection catalogs because those require discovery, dedupe, media policy, and inventory fit checks.
--topic : Focus on a specific topic or concept (matches against tags and titles)
--sources : Comma-separated list of specific wiki article paths to use
--with : Load a supplementary wiki as additional context. The primary wiki (--wiki) provides the subject (what to write about); --with wikis provide craft/skill knowledge (how to write it). Multiple --with flags allowed. Example: --wiki quantum-computing --with article-writing uses quantum-computing for domain content and article-writing for structure, hooks, and writing techniques.
--retardmax: Ship it NOW. Don't agonize over structure or completeness. Generate a rough-but-useful output fast, covering everything the wiki has. Better to have something imperfect now than something perfect never.
--include-archived: Explicitly allow archived primary or supplementary wiki context. Label archived-derived material in the generated output.

Read the full file on GitHub · 103 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.

1mo ago First seen · 103 lines · 33 tokens per session scan A 986a467b7316

Subscribe to this mod's changes

output is a command published in the GitHub repository nvk/llm-wiki (1,422 stars, last pushed 15d ago), licensed MIT. It adds 33 tokens to every session and 1,730 once invoked, about $0.0001 per session on Opus 5.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.

Claude Code Documents LLM agentic-ai agentic-skills agentic-workflow codex

output

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Your task

Parse $ARGUMENTS

What this file has done since we first saw it

Other commands, from other repositories

project

spreadsheet-audit

test-feature

specify

legal-5step

resolve-conflict