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.
git clone --depth 1 https://github.com/regexp-lin/llm-wiki-agentWrote 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/regexp-lin/llm-wiki-agent/wiki-conventions)<a href="https://agentmods.dev/rules/regexp-lin/llm-wiki-agent/wiki-conventions"><img src="https://agentmods.dev/badge/rules/regexp-lin/llm-wiki-agent/wiki-conventions.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.1 | $0.00281 | $0.00281 |
| Opus 5 | $0.00140 | $0.00140 |
| Sonnet 5 | $0.00056 | $0.00056 |
| Haiku 4.5 | $0.00028 | $0.00028 |
Grade A, and why
wiki-conventions 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 7d 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
Wiki Base Conventions
Schema
Read WIKI_SCHEMA.md at the project root for the full wiki data model.
Immutability
raw/is immutable — never modify source documentswiki/is agent-owned — only the agent writes heregraph/is auto-generated output
Naming
- Source pages:
wiki/sources/<kebab-case>.md - Entity pages:
wiki/entities/<TitleCase>.md - Concept pages:
wiki/concepts/<TitleCase>.md - Use
[[PageName]]wikilinks to cross-reference
Index & Log
- Update
wiki/index.mdon every content change - Append to
wiki/log.mdwith format:## [YYYY-MM-DD] <op> | <title>
Available Workflows
Use the corresponding skill by saying one of these triggers:
- Ingest:
ingest <file>oringest(batch) — ingest source documents - Query:
query: <question>— search the knowledge base - Lint:
lint— health-check the wiki - Graph:
build graph— build the knowledge graph
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.
- 7d ago First seen · 32 lines · 281 tokens per session scan A a5334a7f2a13
wiki-conventions is a cursor rule published in the GitHub repository regexp-lin/llm-wiki-agent (15 stars, last pushed 5mo ago), licensed MIT. It adds 281 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-08-30.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.