wiki-record

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

A command that records how a completed task was solved in a wiki's working-memory section. It captures the useful sequence of actions and decisions, rather than only the final result.

In plain words
What is it for?
Use it after completing a task to save the approach and outcome, then optionally create a reusable skill from the experience.
Why use it?
It prevents effective workflows from being forgotten after a task ends. Reusable lessons can be turned into a skill for future work.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Good fit Use it after completing a task to save the approach and outcome, then optionally create a reusable skill from the experience.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/zosmaai/pi-llm-wiki/wiki-record
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/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-record

README.md
[![agentmods](https://agentmods.dev/badge/commands/zosmaai/pi-llm-wiki/wiki-record.svg)](https://agentmods.dev/commands/zosmaai/pi-llm-wiki/wiki-record)
Your own site
<a href="https://agentmods.dev/commands/zosmaai/pi-llm-wiki/wiki-record"><img src="https://agentmods.dev/badge/commands/zosmaai/pi-llm-wiki/wiki-record.svg" alt="Measured on agentmods" height="20"></a>
Per session 28 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 472 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00028 $0.00472
Opus 5 $0.00014 $0.00236
Sonnet 5 $0.00006 $0.00094
Haiku 4.5 $0.00003 $0.00047

Measured 8d ago against content hash 63639d528cce, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

wiki-record 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 8d 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-record.md · 37 lines

What it actually says

/wiki-record

Capture the trajectory of the task you just completed — the sequence of tool calls that solved it — into the wiki's working-memory layer.

This is the counterpart to source capture: instead of recording what you read, it records what you did, so the wiki compounds over your own work.

User Arguments

$ARGUMENTS

Read the LLM Wiki skill at .pi/skills/llm-wiki/SKILL.md first to understand the wiki conventions.

Steps

  1. Call wiki_capture_trajectory with:
    • title: short descriptive phrase for the task (≤60 chars, noun phrase)
    • outcome: optional — success (default), failure, or partial
    • The extension auto-extracts the tool-call trajectory from the live session, so you usually do not pass steps manually.
  2. Open the generated skeleton case page in wiki/cases/ and flesh out:
    • Task — what was requested
    • Approach — the key steps and decisions (not every tool call, just the meaningful ones)
    • Outcome — the result, and anything worth reusing or avoiding next time
  3. If the task taught a reusable pattern, run wiki_distill_skills and create a skill page via wiki_ensure_page(type="skill") that cites [[trajectories/TRJ-...]].
  4. Confirm the case (and any skill) will be surfaced by wiki_recall / wiki_recall_skill in future sessions.

Rules:

  • Only record tasks worth learning from — non-trivial debugging, refactors, integrations, multi-step workflows. Skip trivial one-shot answers.
  • The raw trajectory packet under raw/trajectories/ is immutable. Edit the case/skill pages, never the packet.
  • One trajectory per wiki_capture_trajectory call.
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. 8d ago First seen · 37 lines · 28 tokens per session scan A 63639d528cce

Subscribe to this mod's changes

wiki-record is a command published in the GitHub repository zosmaai/pi-llm-wiki (560 stars, last pushed 3d ago), licensed MIT. It adds 28 tokens to every session and 472 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.