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/quinnjr/fruityloops-mcp/documentationgit clone --depth 1 https://github.com/quinnjr/fruityloops-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.01240 | $0.01240 |
| Opus 5 | $0.00620 | $0.00620 |
| Sonnet 5 | $0.00248 | $0.00248 |
| Haiku 4.5 | $0.00124 | $0.00124 |
Grade A, and why
documentation 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 — 277 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Rules
Documentation Requirements
All features must be documented.
Documentation is as important as code. Users should be able to understand and use features without reading the source code.
Documentation Structure
docs/
├── index.md # Home page
├── installation.md # Installation guide
├── quick-start.md # Quick start
├── usage.md # Usage examples
├── fl-studio-integration.md # FL Studio integration
├── midi-integration.md # MIDI integration
├── mcp-client-setup.md # MCP client setup
├── configuration.md # Configuration
├── contributing.md # Contributing guide
├── development.md # Development setup
├── testing.md # Testing guide
├── git-workflow.md # Git workflow
├── release-process.md # Release process
├── api/
│ ├── server.md # Server API reference
│ └── midi.md # MIDI API reference
└── stylesheets/
└── extra.css # Custom styles
Documentation Tools
MkDocs with Material theme:
# Install docs dependencies
uv sync --extra docs
# Serve locally
uv run mkdocs serve
# Visit http://localhost:8000
# Build documentation
uv run mkdocs build
# Deploy to GitHub Pages
uv run mkdocs gh-deploy --force
Writing Documentation
Use Clear Language
- Write for users, not developers
- Use simple, direct language
- Include examples
- Add code snippets where helpful
Code Examples
Always include working code examples:
## Sending a MIDI Note
```python
from fruityloops_mcp.midi_interface import MIDIInterface
# Create interface
midi = MIDIInterface()
# Connect
midi.connect()
# Send middle C
midi.send_note_on(60, 100)
# Disconnect
midi.disconnect()
```
API Documentation
Use Google-style docstrings - they're auto-generated into docs:
def my_function(param: str, count: int = 10) -> list[str]:
"""Process the parameter and return results.
This function takes a string parameter and processes it
based on the count value provided.
Args:
param: The input string to process
count: Number of items to return, default 10
Returns:
List of processed strings
Raises:
ValueError: If param is empty
Example:
>>> my_function("test", 5)
['test_0', 'test_1', 'test_2', 'test_3', 'test_4']
"""
# Implementation
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 · 277 lines · 1,240 tokens per session scan A a70f301e2b0b
documentation is a cursor rule published in the GitHub repository quinnjr/fruityloops-mcp (5 stars, last pushed 8mo ago), licensed MIT. It adds 1,240 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
android-viewmodel
Android ViewModel conventions — StateFlow, repository abstraction, coroutines, no LiveData.
livkiet-plugins-playai
Agent Framework plugin for voice synthesis with PlayAI API.
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.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.