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/bug-breeder/quip-mcp/cursorrulesgit clone --depth 1 https://github.com/bug-breeder/quip-mcpWhat 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 | $0.01892 | $0.01892 |
| Opus 5 | $0.00946 | $0.00946 |
| Sonnet 5 | $0.00378 | $0.00378 |
| Haiku 4.5 | $0.00189 | $0.00189 |
Grade A, and why
cursorrules 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 yesterday.
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 — 278 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quip MCP Server - Cursor Development Rules
You are an expert Go developer working on a Model Context Protocol (MCP) server for Quip integration. Follow these comprehensive guidelines to ensure code quality, maintainability, and reliability.
Development Philosophy
- Test-Driven Development (TDD): Write tests BEFORE implementing functionality
- SOLID Principles: Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, Dependency Inversion
- Clean Code: Write self-documenting, readable, and maintainable code
- Performance & Security: Optimize for both performance and security from the start
- Documentation: Code should be self-documenting with comprehensive comments for complex logic
Go-Specific Best Practices
Code Structure & Organization
- Use clear, descriptive package names that reflect their purpose
- Group related functionality into appropriate packages (
pkg/quip,pkg/server,pkg/config) - Follow Go naming conventions: PascalCase for exported, camelCase for unexported
- Use meaningful variable and function names that explain intent
- Keep functions small and focused on a single responsibility
Error Handling
- Always handle errors explicitly using Go's idiomatic error handling
- Wrap errors with context using
fmt.Errorf("context: %w", err) - Use typed errors for domain-specific error handling
- Log errors at appropriate levels with structured logging
- Return early on errors (guard clauses)
HTTP & API Integration
- Use context.Context for all HTTP requests with appropriate timeouts
- Implement proper request/response body handling with defer close
- Use structured logging for API requests and responses
- Implement retry logic with exponential backoff for transient failures
- Validate all inputs and sanitize outputs
Concurrency & Performance
- Use goroutines and channels appropriately for concurrent operations
- Implement proper synchronization with mutexes when needed
- Use buffered channels to prevent goroutine leaks
- Profile and benchmark performance-critical code paths
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.
- yesterday First seen · 278 lines · 1,892 tokens per session scan A cbfc2151ec5f
cursorrules is a cursor rule published in the GitHub repository bug-breeder/quip-mcp (2 stars, last pushed 1y ago), licensed MIT. It adds 1,892 tokens to every session, about $0.0095 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-31.
Other cursor rules, from other repositories
swift-development
Swift development: SwiftUI, Combine, async/await, iOS patterns, and Apple platform conventions.
cursorrules
When the user asks about social media, use social-media-ai-mcp tools: schedulepost, generatehashtags, analyzeengagement, plancontentcalendar, getaudienceinsights.
cursorrules
This is an MCP (Model Context Protocol) server that provides Notion integration tools and AI agent workflows. Built with TypeScript, using the MCP SDK for server implementation.
lighter-safety
Safety contract for the Lighter MCP server. Apply whenever a lighter tool is invoked.
terminal-commands
Guidelines for generating terminal commands that ensure outputs are readable by Cursor agents.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.