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.
npx agentmods add instructions/nimachu/my-wiki/agents-mdgit clone --depth 1 https://github.com/NimaChu/my-wikiWhat 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 | $0.00617 | $0.00617 |
| Opus 5 | $0.00309 | $0.00309 |
| Sonnet 5 | $0.00123 | $0.00123 |
| Haiku 4.5 | $0.00062 | $0.00062 |
Grade A, and why
my-wiki AGENTS.md 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 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.
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.
How it starts
The opening of the file, as written. The whole thing — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.
My Wiki Agent Project
This repository is the runnable My Wiki application. It is neither a knowledge vault nor merely an installed Agent Skill.
Project Map
scripts/contains the CLI and knowledge-maintenance implementation.assets/dashboard/contains the web application and local service.deploy/contains standalone deployment options.tests/covers application and workflow contracts.my-wiki-skill/SKILL.mdis the canonical Agent playbook for capture, query, maintenance, evidence, galaxies, sharing, and Dashboard operations.- The user's vault is external to this repository and owns root
index.md/log.md,concepts/,references/, templates, and.my-wiki/runtime state.
The project can run directly with npm run wiki -- <command> and does not require a globally installed Skill. The adapter under my-wiki-skill/ is optional for Agents working from other workspaces.
Knowledge Model
Use the native OKF terms in explanations and new documentation: a durable knowledge page is a Concept, captured evidence is a Reference, and the preserved binary or webpage snapshot is an original. My Wiki visualizes Concepts as concept planets grouped into knowledge galaxies. Historical command names, internal variables, and package fields may still contain wiki, raw, or universe for compatibility; do not infer the old wiki/ or raw/ directories from those identifiers.
Route Requests
Classify the request before acting:
- Knowledge operation: For capturing sources, answering knowledge questions, searching the vault, maintaining knowledge, inspecting evidence, managing galaxies, importing/exporting, or opening the Dashboard, read
my-wiki-skill/SKILL.mdfirst and follow the relevant reference it names. Ordinary questions about concepts, people, products, methods, events, companies, or named projects belong to this route unless the user explicitly asks about repository code. - Project development: For implementation, architecture, tests, bugs, CLI behavior, frontend behavior, or deployment code, work from this repository and preserve its existing engineering patterns.
- Installation or bootstrap: Enter setup only when the user asks to install/configure My Wiki or when the operational playbook reports that the project registration or vault is missing. Follow the README and Skill guidance; do not repeat initialization during normal use.
- Repository publishing: Code may be committed and pushed when requested. Vault knowledge, originals, exports, credentials, and local runtime state must never enter this repository.
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.
- 3d ago First seen · 37 lines · 617 tokens per session scan A 21b088cfc98c
my-wiki AGENTS.md is an instructions file published in the GitHub repository NimaChu/my-wiki (123 stars, last pushed 3d ago), licensed MIT. It adds 617 tokens to every session, about $0.0031 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.
Other instructions, from other repositories
siyuan AGENTS.md
AGENTS.md instructions for siyuan-note/siyuan, covering agents.md, 1. non-negotiable constraints, do not hand-edit, verification and prohibited operations and 2. project-specific rules.
kb AGENTS.md
Instructions for hraness/kb, a project described as: A knowledge base for coding agents, built from Markdown, backlinks, semantic search, and Git context.
living-wiki CLAUDE.md
Claude Code instructions for bronsonelliott/living-wiki, covering claude.md, what this is, architecture, about the user and brain dump parsing flow.
pi-llm-wiki AGENTS.md
Instructions for zosmaai/pi-llm-wiki, covering agents.md, project, tech stack, file layout and conventions.
stashbase AGENTS.md
Instructions for liliu-z/stashbase, covering agent maintenance contract for this repo, github access for this repository, temporary worktrees, electron launch environment and documentation route.
Starcat AGENTS.md
Instructions for starcat-app/Starcat, covering agents.md, 🚨 硬性铁律（每次写代码前必读，违反即返工）, 🌿 git 分支与 worktree（强制）, 🧭 主进度索引（每次开工前必读） and 状态符号（与功能实现总览.md 同步）.