agentmods.dev

wiki-req

wiki-req is a command for Claude Code from zosmaai/pi-llm-wiki. It costs 38 tokens per session (721 once invoked), scanned A, original, MIT.

A command that turns a clarified idea into small, traceable requirements stored as pages in a project wiki. A wiki is a collection of linked documentation pages; the command also preserves the clarified original idea as a separate source record.

In plain words
What is it for?
Use it to clarify scope, assumptions, actors, providers, and fallback behavior, then create atomic requirement pages with status tracking in the wiki.
Why use it?
It helps resolve vague requirements before implementation and breaks large requests into pieces that can be tracked individually. It keeps the original wording available so later requirements can be checked against it.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter.

not rated 556 +4 yesterday A scan 38 tokens original MIT
View the source file zosmaai/pi-llm-wiki zosmaai.github.io
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/zosmaai/pi-llm-wiki/wiki-req
Clone the repo
git clone --depth 1 https://github.com/zosmaai/pi-llm-wiki

Made for: Claude Code.

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 wiki-req

README.md
[![agentmods](https://agentmods.dev/badge/commands/zosmaai/pi-llm-wiki/wiki-req.svg)](https://agentmods.dev/commands/zosmaai/pi-llm-wiki/wiki-req)
Your own site
<a href="https://agentmods.dev/commands/zosmaai/pi-llm-wiki/wiki-req"><img src="https://agentmods.dev/badge/commands/zosmaai/pi-llm-wiki/wiki-req.svg" alt="Measured on agentmods" height="20"></a>
Per session 38 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 721 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.1 $0.00038 $0.00721
Opus 5 $0.00019 $0.00360
Sonnet 5 $0.00008 $0.00144
Haiku 4.5 $0.00004 $0.00072

Measured 6d ago against content hash 5ea5e1a947d5, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

wiki-req 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 6d 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.

commands/wiki-req.md · 57 lines

How it starts

The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/wiki-req

Capture a concept and decompose it into atomic, traceable requirements in the wiki.

Transforms natural language descriptions into structured wiki/requirements/ pages, preserving the original clarified concept as an immutable source packet in raw/sources/.

User Arguments

$ARGUMENTS

Read the LLM Wiki skill at .pi/skills/llm-wiki/SKILL.md first to understand the wiki conventions, architecture, and page type rules.

Steps

  1. Clarify the concept

    • Discuss with the user: unpack ambiguous terms, surfaces implicit assumptions, identify scope boundaries
    • Ask targeted questions to resolve unknowns (e.g., "Which providers?", "What's the fallback behavior?", "Who are the actors?")
    • Reach mutual clarity before proceeding

  2. Capture the clarified concept

    • Call wiki_capture_source(text=...) with the clarified conversation as markdown
    • This creates an immutable record in raw/sources/SRC-YYYY-MM-DD-NNN/
    • The source captures the original intent verbatim — no interpretation, no decomposition

  3. Decompose into atomic requirements

    • Break the clarified concept into the smallest meaningful units of functionality
    • Each requirement should represent one independently verifiable behavior
    • For each atomic requirement, call wiki_ensure_page(type="requirement", title="...", content="...") where content includes:
      • type: requirement and status: draft in frontmatter
      • A clear ## Description section
      • ## Acceptance Criteria as a checkbox list (the threshold for "done")
      • source_id linking back to the source capture
      • depends_on linking to any prerequisite requirements
      • [[wikilinks]] to relevant entities, concepts, and other wiki pages
    • Set priority based on user input: p0 (blocking), p1 (critical), p2 (important), p3 (nice-to-have)

  4. Cross-link and finalize

    • Ensure each requirement page has bidirectional wikilinks to related pages
    • Update any existing entity or concept pages that these requirements reference
    • Report the results: how many requirements created, their priorities, and the source capture ID

Read the full file on GitHub · 57 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. 6d ago First seen · 57 lines · 38 tokens per session scan A 5ea5e1a947d5

Subscribe to this mod's changes

wiki-req is a command published in the GitHub repository zosmaai/pi-llm-wiki (556 stars, last pushed yesterday), licensed MIT. It adds 38 tokens to every session and 721 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.

Memory and contextPlanningkarpathyknowledge-basellm-wikimarkdownobsidian
Related

Other commands, from other repositories

build

Rebuild context.md for a project from sources/. Usage: /mb:build [-p ] [project-id].

frankchu91/mindbase-llm-wiki · 26 tokens

lint

Run health check on a project — orphans, contradictions, stale claims, gaps, suggested cross-links. Usage: /mb:lint [-p ] [project-id].

frankchu91/mindbase-llm-wiki · 37 tokens

ask

Query the MindBase wiki — cited answer using hybrid search + graph expansion. Usage: /mb:ask [-p ] [--all-projects].

frankchu91/mindbase-llm-wiki · 36 tokens

load

Explicitly load a project's context into session (overrides SessionStart hook). Usage: /mb:load [project-id].

frankchu91/mindbase-llm-wiki · 25 tokens

init_newbrain

Onboarding interativo que personaliza AGENTS.md, Memória/ e a estrutura inicial do vault.

PedroHenrique0713/brain-template · 24 tokens

vault_gc

Manutenção semanal do vault: arquiva handovers antigos, valida Memória/INDEX.md e triage do INBOX.

PedroHenrique0713/brain-template · 27 tokens