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/viktor-silakov/mac-say-mcp/cursorrulesgit clone --depth 1 https://github.com/viktor-silakov/mac-say-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.01247 | $0.01247 |
| Opus 5 | $0.00624 | $0.00624 |
| Sonnet 5 | $0.00249 | $0.00249 |
| Haiku 4.5 | $0.00125 | $0.00125 |
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 2d 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cursor IDE Rules for mac-say-mcp Development
Project Context
This is a Model Context Protocol (MCP) server for text-to-speech using macOS say command. It provides TTS capabilities through MCP tools for various clients (Claude, VS Code, etc.). macOS ONLY - requires the say command.
Development Workflow Rules
🧪 Testing Requirements
- ALWAYS test manually after ANY code change with real MCP clients
- Test ALL TTS tools (speak, save_audio, list_voices, voice_demo, system_info)
- Test with different voices, rates, and text inputs
- Test audio file generation and verify file creation
- Test error cases (invalid voices, long text, special characters)
- Clean up generated audio files after testing
📝 Documentation Requirements
- Update README.md for every significant change
- Document new MCP tools with proper JSON schema and examples
- Document macOS compatibility requirements
- Include tool usage examples in JSON format
- Update voice support information when applicable
- All documentation and comments must be in English
🔧 Code Quality Rules
- Follow ES6+ module syntax (import/export)
- Handle error cases gracefully with proper error messages
- Use meaningful variable and function names
- Add JSDoc comments for complex functions
- Validate MCP tool parameters before processing
- Ensure consistent async/await patterns
- All code comments must be in English
📁 File Organization
- Main server code in
index.js(entry point) - Audio files generated in
audio/directory - Documentation in
README.mdandAI_MANUAL_TESTING_AGENT.md - Keep structure simple - single file architecture for now
- Audio directory auto-created if missing
🚀 Enhancement Process
- Identify TTS requirement clearly in documentation
- Test with
saycommand manually first - Implement MCP tool with proper schema validation
- Test with MCP client (Claude Desktop, VS Code MCP)
- Update README.md with tool examples
- Test edge cases (long text, special chars, invalid params)
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.
- 2d ago First seen · 144 lines · 1,247 tokens per session scan A ebc54afafc87
cursorrules is a cursor rule published in the GitHub repository viktor-silakov/mac-say-mcp (1 stars, last pushed 1y ago), licensed MIT. It adds 1,247 tokens to every session, about $0.0062 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
02-cms-assets
Advise developers on organizing, delivering, and transforming assets in Contentstack. Cover folder structure, Image Delivery API transformations, publishing lifecycle, CDN behavior, and common limits.
ableton-cli
This repo controls Ableton Live via a local Remote Script.
creative-mode-map
Cursor rule "creative-mode-map" from giang6283623/cursor-tip, covering creative mode: design process map, 🧭 creative mode process flow, 📋 creative phase document format, 🔍 creative types and approaches and 📊 required file state verification.
080-creative-phase-metrics
description: WHEN entering a creative phase ENSURE comprehensive exploration and validation globs: ["/.md", "/.mdc"] alwaysApply: true.
livkiet-plugins-playai
Agent Framework plugin for voice synthesis with PlayAI API.
java-8
List names = users.stream() .map(User::getName) .filter(name -> name != null && !name.isEmpty()) .collect(Collectors.toList()).