A workflow for rebuilding a project wiki from a codebase using the mimirs wiki tool. The wiki is organized around concrete flows such as routes, event handlers, command-line commands, tools, and scheduled jobs.

Use it to generate, rebuild, refresh, or write a flow-focused wiki for a codebase.

It helps keep documentation tied to real ways the system is used instead of producing broad pages that may be hard to maintain or verify.

wiki — Skill for Claude Code by TheWinci/mimirs

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.

Any agent

npx skills add TheWinci/mimirs --skill wiki

Clone the repo

git clone --depth 1 https://github.com/TheWinci/mimirs

Made for: Claude Code.

Or install mimirs, the plugin that ships this one along with the rest of its 11 skills, 3 hooks.

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/skills/thewinci/mimirs/wiki/github.svg)](https://agentmods.dev/skills/thewinci/mimirs/wiki)

Your own site

<a href="https://agentmods.dev/skills/thewinci/mimirs/wiki"><img src="https://agentmods.dev/badge/skills/thewinci/mimirs/wiki/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/skills/thewinci/mimirs/wiki"><img src="https://agentmods.dev/badge/skills/thewinci/mimirs/wiki.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,569 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.00038	$0.01569
Opus 5.5	$0.00015	$0.00628
Sonnet 5.5	$0.00008	$0.00314
Haiku 4.5	$0.00004	$0.00157

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

Security

Grade A, and why

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

skills/wiki/SKILL.md · 139 lines

How it starts

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

Wiki Rebuild

Use the wiki MCP tool as the source of truth. This skill is only a workflow wrapper; do not invent a separate wiki structure.

The generation prose — discovery rules, the source-first writing contract, the self-check, and the per-page prompts (flow, screen, overview, mechanism) — is served from markdown, using packaged defaults unless a project overrides them. To customize it for a project, run wiki(eject) once: it writes the defaults to .mimirs/wiki/*.md for you to edit, and a file there overrides the packaged default. Edit instructions in .mimirs/wiki/, never the generated wiki/ output.

Core Rule

The wiki is flow-first. Create one page for one concrete trigger:

one HTTP method + route
one message, event, queue topic, or consumer handler
one CLI subcommand
one MCP tool
one worker, job, schedule, webhook, or server start

Do not bundle all API endpoints into one page. Do not bundle all messages into one page. Do not create broad architecture, module, entity, glossary, or generic data-flow pages unless the human explicitly asks for those.

The sanctioned exception for shared internals is a mechanism page (kind: "mechanism", slug mechanisms/<name>): one page per internal subsystem that three or more flows call but that is nobody's entry point — ranking, caching, graph traversal, or similar. Flow pages link to it instead of each re-explaining the same internals.

If many flows share files, keep separate pages and connect them with related flows.

Workflow

Call index_files() if the project index is empty or stale.
Call wiki(shape).
Use the returned prompt and prefetch selectors to create wiki/_discovery.json (flows first, then the overview second pass, then the mechanism third pass).
Validate with wiki(validate-discovery).
If validation reports errors, fix wiki/_discovery.json and validate again.
If validation passes, ask the human whether to continue.
If the human says yes, call wiki(write).
Read wiki(discovery) and split the work by page slug.
For each slug, call wiki(write:page:<slug>).
Write only the assigned page under wiki/.
After all page writers finish, call wiki(validate-pages) and fix any broken relative .md links it reports.
Before committing the updated pages, call wiki(changelog) and follow the returned prompt: it diffs the pending wiki/ changes and has you prepend one entry to wiki/CHANGELOG.md — a curated summary of the behavior changes for an incremental update, or a single line for a full regeneration. Then commit the pages and the changelog together.

Read the full file on GitHub · 139 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 · 139 lines · 38 tokens per session scan A 206b1c766305

Subscribe to this mod's changes

wiki is a skill published in the GitHub repository TheWinci/mimirs (30 stars, last pushed 6d ago), licensed Apache-2.0. It adds 38 tokens to every session and 1,569 once invoked, about $0.0002 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 Writing and docs ai-coding code-search llm-tools mcp mcp-server

research

Performs deep research on a topic via deepresearch. Simulates a multi-step research process and returns a comprehensive research result as a string.

study8677/repobrain · 32 tokens

memorix-sessions

Use when resuming work, preparing handoff context, binding an HTTP control-plane project, or deciding whether sessionstart is useful.

AVIDS2/memorix · 31 tokens

memorix-troubleshooting

Use when Memorix MCP, setup, project binding, HTTP control plane, hooks, skills, or agent integration is missing, stale, or failing.

AVIDS2/memorix · 36 tokens

azure-event-grid-webhooks

Receive and validate Azure Event Grid webhook deliveries. Use when setting up an Event Grid WebHook event handler, implementing the Microsoft.EventGrid.SubscriptionValidationEvent handshake (echo data.validationCode as validationResponse with HTTP 200), implementing the CloudEvents v1.0 HTTP OPTIONS abuse-protection…

hookdeck/webhook-skills · 148 tokens

formstack-webhooks

Receive and verify Formstack Forms webhooks (the "WebHook" submit action, aka "Send Data to an External URL"). Use when setting up a Formstack form submission webhook handler, debugging X-FS-Signature HMAC verification, handling application/x-www-form-urlencoded or JSON submission payloads, or working out which fields…

hookdeck/webhook-skills · 108 tokens

circleci-webhooks

Receive and verify CircleCI outbound webhooks. Use when setting up a CircleCI webhook handler, debugging circleci-signature verification, or handling the workflow-completed and job-completed events CircleCI sends when a workflow or job reaches a terminal state. CircleCI signs the raw body with HMAC-SHA256 and sends a…

hookdeck/webhook-skills · 150 tokens