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/hiromaily/go-crypto-wallet/documentation-languagegit clone --depth 1 https://github.com/hiromaily/go-crypto-walletWrote 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/hiromaily/go-crypto-wallet/documentation-language)<a href="https://agentmods.dev/rules/hiromaily/go-crypto-wallet/documentation-language"><img src="https://agentmods.dev/badge/rules/hiromaily/go-crypto-wallet/documentation-language.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.00000 | $0.00219 |
| Opus 5 | $0.00000 | $0.00110 |
| Sonnet 5 | $0.00000 | $0.00044 |
| Haiku 4.5 | $0.00000 | $0.00022 |
Grade A, and why
documentation-language 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 5d 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
Documentation Language Rules
Overview
All documentation files (.md, .mdc) in this project must be written in English.
Rules
-
Write all documentation in English
- README files
- Technical documentation
- Code comments in markdown
- Rule files (
.claude/rules/,.cursor/rules/) - Skill files (
.claude/skills/,.cursor/skills/)
-
Exceptions
- Inline code comments in source files may use Japanese if necessary for clarity
- User-facing messages that require localization
-
Consistency
- Use American English spelling (e.g., "color" not "colour")
- Use consistent terminology throughout the project
Rationale
- English documentation ensures accessibility for international contributors
- Maintains consistency across the codebase
- Facilitates collaboration with global developer community
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.
- 5d ago First seen · 38 lines · 0 tokens per session scan A aec2b3c91dcd
documentation-language is a cursor rule published in the GitHub repository hiromaily/go-crypto-wallet (127 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 219 tokens. 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-01.
Other cursor rules, from other repositories
documentation
Documentation discovery index for Lineth monorepo.
design-system
../../.agents/rules/design-system.md.
env-vars
../../.agents/rules/env-vars.md.
tests-unit
../../.agents/rules/tests-unit.md.
tests-visual
../../.agents/rules/tests-visual.md.
typescript
../../.agents/rules/typescript.md.