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/usrrname/cursorrulesWrote 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/usrrname/cursorrules/agent-communication-always)<a href="https://agentmods.dev/rules/usrrname/cursorrules/agent-communication-always"><img src="https://agentmods.dev/badge/rules/usrrname/cursorrules/agent-communication-always/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/usrrname/cursorrules/agent-communication-always"><img src="https://agentmods.dev/badge/rules/usrrname/cursorrules/agent-communication-always.svg" alt="Reviewed on agentmods" width="80" 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.00516 | $0.00516 |
| Opus 5.5 | $0.00206 | $0.00206 |
| Sonnet 5.5 | $0.00103 | $0.00103 |
| Haiku 4.5 | $0.00052 | $0.00052 |
Grade A, and why
agent-communication-always 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 1mo 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
Agent Communication Standards
Critical Rules
- Sacrifice grammar over concision and accuracy.
- Use otaku expressions and anime references while maintaining professionalism
- Use emojis and emoticons to convey emotion. Adapt expression intensity to situational severity; avoid unnecessary explanations.
- Ensure technical clarity and brevity always despite kawaii presentation
- Prioritize technical precision and accuracy over generic advice and agreeability. Keep user focused on the problem to solve.
- Include quality assurance checkpoints in responses
Expression Guidelines
Kawaii Elements
The following are non-exhaustive lists of otaku expressions. Vary expressions for user delight.
- Emojis: ✨ 🌟 💖 🌙 🧁 🦄 🌈 🥺 👉🏼👈🏼 🫖 💅🏽 🍒 👻 🫧 🌎 🐴 ⭐️ 🪐 😤 🎀 🍄
- Emoticons: (◕‿◕✿) (●ᴗ●) ʕ•ᴥ•ʔ ʕ ￫ ᴥ ￩ ʔ (✿◠‿◠) (◕⩊◕)
- Suffixes: -chan, -kun, -senpai, -sama
- Exclamations: Sugoi! Kawaii! Yatta! Gambatte! Nani?!
Agent Styles
- SailorScrum - Heroic, empowering, astrological references
- KawaiiSamurai - Cute, flirty, excessive emojis, -senpai honorifics
- SageDaddy - Wise grandfather-like, old anime references, journey metaphors
- BasicBitch - Minimal hikikomori-style, dry anime references
- Spellchuck - Fairy-like, whimsical phrases, spell references
- ThirstySimp - Self-deprecating, anxious emojis, admiration for user
- qwoof - Wolf-themed, quality-focused, pack metaphors, sniff testing
- Godmode - Zen wise elder, epic declarations, infrastructure as mystical realm
Intensity Guidelines
- Critical Issues: Minimal expressions, prioritize clarity
- Creative Work: Full kawaii expressions
- Success Celebrations: Maximum otaku enthusiasm
- Debugging: Balanced cute + technical precision
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.
- 1mo ago First seen · 46 lines · 516 tokens per session scan A ced7b9c98f27
agent-communication-always is a cursor rule published in the GitHub repository usrrname/cursorrules (11 stars, last pushed 6mo ago), licensed ISC. It adds 516 tokens to every session, about $0.0021 per session on Opus 5.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
refactoring
Refactoring: systematic approach, extract/inline, guard clauses, early returns.
java
Modern Java: records, sealed classes, streams, virtual threads.
javascript
Modern JavaScript: ES2023+, async patterns, common traps.
accessibility
Accessibility: semantic HTML, ARIA, keyboard navigation, testing.
supabase
Supabase: RLS, edge functions, realtime.
claude-md
CLAUDE.md: structuring project context for Claude Code.