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/readmegit clone --depth 1 https://github.com/quinnjr/fruityloops-mcpWrote 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/quinnjr/fruityloops-mcp/readme)<a href="https://agentmods.dev/rules/quinnjr/fruityloops-mcp/readme"><img src="https://agentmods.dev/badge/rules/quinnjr/fruityloops-mcp/readme.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 | $0.00681 | $0.00681 |
| Opus 5 | $0.00341 | $0.00341 |
| Sonnet 5 | $0.00136 | $0.00136 |
| Haiku 4.5 | $0.00068 | $0.00068 |
Grade A, and why
README 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 4d 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cursor Rules for FL Studio MCP Server
This directory contains Cursor AI rules that define coding standards, workflows, and conventions for the FL Studio MCP Server project.
Overview
These rules help maintain consistency and quality across the codebase by providing clear guidelines for:
- Git workflow and branching strategy
- Python coding standards
- Testing requirements
- Documentation practices
- Project-specific conventions
Rule Files
git-workflow.mdc
Critical git workflow rules, including:
- ⛔ Never use
--no-verify(most important rule) - Git-flow branching model
- Commit message format (Conventional Commits)
- Pull request workflow
- Tag and release management
python-testing.mdc
Python development and testing standards:
- Testing requirements (90% coverage minimum)
- Using
uvas package manager - Code quality with Ruff
- Type hints and docstrings
- Async/await patterns
- Error handling
documentation.mdc
Documentation guidelines:
- MkDocs usage and structure
- Writing clear documentation
- API documentation generation
- Code examples in docs
- Changelog management
project-conventions.mdc
Project-specific conventions:
- Module organization
- Naming conventions
- FL Studio API handling
- MIDI best practices
- Testing patterns
- Release process
Using These Rules
Cursor AI will automatically reference these rules when:
- Writing new code
- Suggesting changes
- Reviewing code
- Answering questions about the project
The rules help ensure that all AI-generated code and suggestions follow project standards.
Critical Rules
🚨 Most Important Rules
-
Never use
--no-verifywith git commands- Git hooks exist for quality control
- Bypassing them defeats their purpose
- Fix issues instead of bypassing checks
-
Always include unit tests
- Minimum 90% coverage
- Tests must pass before committing
-
Always use
uvinstead of pip/npm- Project standard package manager
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.
- 4d ago First seen · 125 lines · 681 tokens per session scan A 0695e9d81ead
README is a cursor rule published in the GitHub repository quinnjr/fruityloops-mcp (5 stars, last pushed 8mo ago), licensed MIT. It adds 681 tokens to every session, about $0.0034 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
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-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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.