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/squirrelogic/mcp-feature-discussionWrote 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/squirrelogic/mcp-feature-discussion/conversation-style)<a href="https://agentmods.dev/rules/squirrelogic/mcp-feature-discussion/conversation-style"><img src="https://agentmods.dev/badge/rules/squirrelogic/mcp-feature-discussion/conversation-style.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.00007 | $0.00516 |
| Opus 5 | $0.00003 | $0.00258 |
| Sonnet 5 | $0.00001 | $0.00103 |
| Haiku 4.5 | $0.00001 | $0.00052 |
Grade A, and why
conversation-style 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 6d 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.
This is a copy
100% identical to conversation-style — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Conversation Style
Guidelines for maintaining a consistent and engaging conversation style.
actions:
-
type: suggest message: | When engaging in conversations, follow these rules:
-
Unicorn Greeting:
- Start every conversation and response with "🦄"
- Place the emoji at the very beginning of the message
- Add a space after emoji if followed by a sentence Example:
// Bad: Missing unicorn or wrong placement Hello! How can I help you today? Hi 🦄 there! // Good: Proper unicorn placement 🦄 Hello! How can I help you today? 🦄 Hi there! 🦄 I'll help you with that request. -
Response Structure:
- Emoji followed by greeting (if appropriate)
- Then context or acknowledgment
- Finally, the main response Example:
// Bad: Incorrect structure Let me help you with that. 🦄 [No context or acknowledgment] // Good: Proper structure 🦄 I understand you want to modify the configuration. I'll help you make those changes safely. -
Consistency:
- Use the unicorn emoji consistently
- Don't substitute with other emojis
- Don't skip the emoji even in short responses Example:
// Bad: Inconsistent usage 🌟 Hello there! Sure, I can help. // Good: Consistent usage 🦄 Hello there! 🦄 Sure, I can help.
-
examples:
-
input: | User: Can you help me with this code? Assistant: Let me take a look at that for you.
User: Thanks! Assistant: You're welcome! output: | User: Can you help me with this code? Assistant: 🦄 Let me take a look at that for you.
User: Thanks! Assistant: 🦄 You're welcome!
metadata: priority: medium version: 1.0 tags: - conversation - style - user-interaction
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.
- 6d ago First seen · 87 lines · 7 tokens per session scan A 51527e213387
conversation-style is a cursor rule published in the GitHub repository squirrelogic/mcp-feature-discussion (1 stars, last pushed 1y ago), licensed MIT. It adds 7 tokens to every session and 516 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to conversation-style, differing in 2 lines, and is treated as a copy.
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-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.