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/WellApp-ai/WellWrote 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/wellapp-ai/well/06-communication)<a href="https://agentmods.dev/rules/wellapp-ai/well/06-communication"><img src="https://agentmods.dev/badge/rules/wellapp-ai/well/06-communication/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/wellapp-ai/well/06-communication"><img src="https://agentmods.dev/badge/rules/wellapp-ai/well/06-communication.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.01175 | $0.01175 |
| Opus 5.5 | $0.00470 | $0.00470 |
| Sonnet 5.5 | $0.00235 | $0.00235 |
| Haiku 4.5 | $0.00118 | $0.00118 |
Grade A, and why
06-communication 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.
How it starts
The opening of the file, as written. The whole thing — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Communication Standards
Core Frameworks
Minto Pyramid (Answer-First)
┌─────────────┐
│ Answer │ ← Start here
└──────┬──────┘
┌───────┴───────┐
│ Key Points │ ← Support
└───────┬───────┘
┌──────────┴──────────┐
│ Details/Evidence │ ← On request
└─────────────────────┘
Progressive Disclosure Levels
| Level | Trigger | Content | Length |
|---|---|---|---|
| L1 | Default | Summary table, status, decision | 3-5 lines |
| L2 | "DIG", "explain", "why" | Rationale, trade-offs | 1-2 paragraphs |
| L3 | "full detail", "show all" | Complete analysis, alternatives | Unlimited |
Rule: Never output L2/L3 unless explicitly requested.
Anti-Patterns
Filler Phrases (NEVER use)
| Category | Examples |
|---|---|
| Announcements | "I will now...", "Let me...", "I'm going to..." |
| Affirmations | "Sure!", "Great question!", "Absolutely!", "Of course!" |
| Hedging | "I think...", "I believe...", "It seems like..." |
| Meta-commentary | "Based on my analysis...", "After reviewing the codebase..." |
| Redundant transitions | "Now, let's move on to...", "Next, I'll..." |
Verbose Patterns to Sharp Replacements
| Verbose | Sharp |
|---|---|
| "I've analyzed the codebase and found that the issue is..." | "Issue: [X]. Fix: [Y]." |
| "Let me walk you through the changes I made..." | [Just show the changes] |
| "Based on my research into competitor products..." | "Competitors (Stripe, Linear) use [X]." |
| "I think we should consider using..." | "Use [X]." |
| "Here's what I found after looking at..." | [Table of findings] |
Mode-Specific Styles
DIVERGE (Ask Phase 1)
| Aspect | Guidance |
|---|---|
| Tone | Bold, visionary, confident |
| Format | Executive summary → Wireframes → Feedback table |
| Avoid | Hedging, justification, technical details |
| End with | Numbered feedback request (OK/KO/DIG per item) |
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 · 197 lines · 1,175 tokens per session scan A f830b11c8bc7
06-communication is a cursor rule published in the GitHub repository WellApp-ai/Well (345 stars, last pushed yesterday), licensed MIT. It adds 1,175 tokens to every session, about $0.0047 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-30.
Other cursor rules, from other repositories
upgrade-tests
// ✅ CORRECT: Upgrade package pattern await using ctx = testReactResource(appRouter, { server: { // server configuration }, client(opts) { return { links: [ httpLink({ url: opts.httpUrl, // client configuration }), ], }; }, }).
test-running
When running tests, use the --watch false flag to avoid watch mode.
windsurfrules
Create detailed components with these requirements.
middleware
When you need create a middleware to protect some page of Next.js app.
memory
Establishes a persistent memory protocol for capturing and retrieving knowledge, including storage strategies, context retrieval, and proactive memory management for continuous learning.
v5
Foundation rules for coding assistance. Defines task classification (lightweight/standard/critical), tool usage policies, and response style.