refresh-wiki

refresh-wiki is a command for coding agents from damusix/atomic-claude. It costs 66 tokens per session (6,524 once invoked), scanned C, original, MIT.

A command for updating a project wiki, either inside the current code repository or in a shared wiki covering multiple repositories. A repository is the project folder containing its code and history.

In plain words
What is it for?
Use it to refresh repository or cross-repository wiki content, optionally providing a root directory when the shared wiki is elsewhere.
Why use it?
It determines which wiki the request refers to and runs the matching update process, avoiding confusion between project documentation and broader team documentation.

Command

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/damusix/atomic-claude/refresh-wiki
Clone the repo
git clone --depth 1 https://github.com/damusix/atomic-claude
Per session 66 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 6,524 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 2 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.00066 $0.06524
Opus 5 $0.00033 $0.03262
Sonnet 5 $0.00013 $0.01305
Haiku 4.5 $0.00007 $0.00652

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

Security

Grade C, and why

refresh-wiki scanned grade C with 2 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 3d 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.

Downloads and executes remote codehighSupply chain

curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.

install: curl -fsSL https://raw.githubusercontent.com/damusix/atomic-claude/main/install.sh | bash

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

install: curl -fsSL https://raw.githubusercontent.com/damusix/atomic-claude/main/install.sh | bash
context/commands/refresh-wiki.md · 542 lines

How it starts

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

/refresh-wiki [root] — refresh the wiki. With no argument, auto-detects scope: if docs/wiki/index.md exists in the current repo the scope is repo; if a wiki/ directory exists at the cwd or a supplied [root] the scope is realm. Pass [root] to target a specific realm root.

Step 0 — Detect scope

Determine which pipeline to run:

Repo scope — all of the following:

  • No [root] argument supplied, AND
  • docs/wiki/index.md exists in the current repo (check test -f docs/wiki/index.md), OR docs/wiki/ exists but is empty / no index yet (first run).

Specifically: if no [root] was supplied and the cwd is inside a git repo, this is repo scope. Continue to the Repo scope steps.

Realm scope — any of the following:

  • [root] argument was supplied, OR
  • No [root] was supplied but a wiki/ directory exists at the cwd that contains an index.md with <wiki-type>realm</wiki-type>, OR
  • The current working directory is not inside a git repo but a wiki/ directory is present.

Continue to the Realm scope steps.

Ambiguous — cwd is a git repo AND a sibling wiki/ directory exists (repo + wiki/ co-located). Ask via AskUserQuestion:

This directory is a git repo and has a wiki/ sibling. Which scope?
- Repo scope (refresh docs/wiki/ inside this repo)
- Realm scope (refresh wiki/ as a cross-repo wiki)

Treat as repo scope on cancel or ambiguous input.


Repo scope

R1 — Pre-flight

git rev-parse --is-inside-work-tree

If not inside a git repo, stop:

not a git repo. /refresh-wiki (repo scope) requires a git repository.
command -v atomic

If atomic is not on $PATH, stop:

atomic binary not found on $PATH.
install: curl -fsSL https://raw.githubusercontent.com/damusix/atomic-claude/main/install.sh | bash
then re-run /refresh-wiki.

R2 — Bootstrap check

test -f docs/wiki/scan.md

If the file does not exist, this is a first-time initialization. Print:

Read the full file on GitHub · 542 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. 3d ago First seen · 542 lines · 66 tokens per session scan C fd762831ea7b

Subscribe to this mod's changes

refresh-wiki is a command published in the GitHub repository damusix/atomic-claude (83 stars, last pushed 9d ago), licensed MIT. It adds 66 tokens to every session and 6,524 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.