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 rules/xccelephant/agent-wiki/llm-wiki-structuregit clone --depth 1 https://github.com/xccElephant/agent-wikiWrote 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/rules/xccelephant/agent-wiki/llm-wiki-structure)<a href="https://agentmods.dev/rules/xccelephant/agent-wiki/llm-wiki-structure"><img src="https://agentmods.dev/badge/rules/xccelephant/agent-wiki/llm-wiki-structure.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.00156 | $0.00156 |
| Opus 5 | $0.00078 | $0.00078 |
| Sonnet 5 | $0.00031 | $0.00031 |
| Haiku 4.5 | $0.00016 | $0.00016 |
Grade A, and why
llm-wiki-structure 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 4d 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.
What it actually says
LLM Wiki Structure
- Treat
raw/as the immutable source layer. - Keep original article notes in
raw/articles/and local attachments inraw/assets/. - Store one derived note per source in
wiki/source-notes/. - Put stable topic pages in
wiki/entities/,wiki/concepts/, orwiki/synthesis/. - Do not silently "upgrade" a raw file into a wiki page. Create a new derived page instead.
- Update
wiki/index.mdwhen adding or renaming a persistent wiki page. - Keep
logs/log.mdappend-only for migrations, ingests, lint passes, and major analyses.
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.
- 4d ago First seen · 15 lines · 156 tokens per session scan A 1ff83d11a49c
llm-wiki-structure is a cursor rule published in the GitHub repository xccElephant/agent-wiki (4 stars, last pushed 4mo ago), licensed MIT. It adds 156 tokens to every session, about $0.0008 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-31.
Other cursor rules, from other repositories
about-this-repo
このリポジトリの背景・概要・目的（OCD MCP プロジェクトコンテキスト）.
workflow
BDD-style workflow, UI screenshots in the PR, HTTP OpenAPI and config schema sync before lint, final checks.
frontend
Demo Shop frontend guidance.
shadcn-tailwind-guide
本规范定义了使用 shadcn/ui 和 Tailwind CSS 开发新组件的标准流程和最佳实践。.
instruct-ut
基于用户的目标，生产 todo list 并按顺序执行.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.