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/janyork/llm-wiki-cli/agents-mdgit clone --depth 1 https://github.com/JanYork/llm-wiki-cliWrote 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.
[](https://agentmods.dev/instructions/janyork/llm-wiki-cli/agents-md)<a href="https://agentmods.dev/instructions/janyork/llm-wiki-cli/agents-md"><img src="https://agentmods.dev/badge/instructions/janyork/llm-wiki-cli/agents-md.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00289 | $0.00289 |
| Opus 5 | $0.00144 | $0.00144 |
| Sonnet 5 | $0.00058 | $0.00058 |
| Haiku 4.5 | $0.00029 | $0.00029 |
Grade A, and why
llm-wiki-cli 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 yesterday.
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.
What it actually says
Project agent brain
- Read
.agents/project-memory.mdat the start of substantive repository work. It owns the concise project map, authoritative documentation map, LWC Wiki entry points, and maintenance triggers. - Use the project LWC Wiki for durable detailed knowledge. Start with
lwc --scope project search "<task terms>" --limit 20, then open only relevant pages and current source/code evidence. - During relevant work and before completion, evaluate whether verified reusable knowledge should update the Wiki or
.agents/project-memory.md. Make no memory change when nothing qualifies. Update this discovery map in the same task whenever brain structure changes. - Require a resolved safety notice and a separate human confirmation only for materially destructive or hard-to-recover actions, credential/secret handling, privilege or security-boundary changes, permanent deletion, history rewriting/force-push, and production publication that the user did not already explicitly authorize. Ordinary explicitly requested Git commits, fast-forward merges, and non-force pushes need no extra confirmation after scope checks.
- Reconfirm only when the target, affected user data, destructive method, or risk class materially changes. Incidental details such as discovered file counts, generated commit hashes, or equivalent safe command syntax do not invalidate authorization. Never expose or persist literal secrets.
- Archive before permanent deletion of brain knowledge.
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.
- yesterday First seen · 11 lines · 289 tokens per session scan A 1ddee21bf40f
llm-wiki-cli AGENTS.md is an instructions file published in the GitHub repository JanYork/llm-wiki-cli (52 stars, last pushed today), licensed Apache-2.0. It adds 289 tokens to every session, about $0.0014 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-09-03.
Other instructions, from other repositories
Acontext AGENTS.md
Instructions for memodb-io/Acontext, covering acontext, navigation guide, plan-driven development, modules and rules.
openwebui-extensions copilot-instructions.md
Copilot instructions for Fu-Jie/openwebui-extensions, covering copilot instructions for openwebui-extensions, 🏗️ 项目结构与命名 (project structure & naming), 1. 语言与代码规范 (language & code requirements), 2. 插件目录结构 (plugin directory structure) and 3. 文档字符串规范 (docstring standard).
powercontext AGENTS.md
AGENTS.md instructions for oceanbase/powercontext, covering repository guidelines, project structure & module organization, build, test, and development commands, agent skills and coding style & naming conventions.
Plugin Documentation
Use when writing or updating plugin README files, mirrored docs pages, bilingual release notes, or other user-facing documentation for plugins.
openwebui-extensions GEMINI.md
Gemini CLI instructions for Fu-Jie/openwebui-extensions, covering openwebui extensions — gemini cli project context, project overview, non-negotiable rules, plugin file contract and docstring (required fields).
Commit Message
Comprehensive Conventional Commits guidelines for openwebui-extensions.