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/python-testinggit 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.01154 | $0.01154 |
| Opus 5 | $0.00577 | $0.00577 |
| Sonnet 5 | $0.00231 | $0.00231 |
| Haiku 4.5 | $0.00115 | $0.00115 |
Grade A, and why
python-testing 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 — 238 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Python and Testing Rules
Testing Requirements
Unit Tests are Mandatory
All new code must include unit tests.
- Minimum 90% code coverage
- Tests must pass before committing
- Use Vitest for TypeScript/JavaScript, pytest for Python
Running Tests
# Run all tests
uv run pytest
# Run with coverage
uv run pytest --cov=src/fruityloops_mcp --cov-report=term-missing
# Run specific test file
uv run pytest tests/test_server.py
# Run specific test
uv run pytest tests/test_server.py::TestFLStudioMCPServer::test_initialization
Writing Tests
Follow pytest conventions:
# File: tests/test_feature.py
import pytest
from fruityloops_mcp.module import Feature
class TestFeature:
"""Test suite for Feature class."""
def test_basic_functionality(self):
"""Test basic functionality."""
feature = Feature()
result = feature.do_something()
assert result is not None
@pytest.mark.asyncio
async def test_async_functionality(self):
"""Test async functionality."""
feature = Feature()
result = await feature.do_async()
assert result == expected_value
Test Organization
tests/
├── __init__.py
├── test_server.py # Server tests
├── test_midi.py # MIDI interface tests
├── test_integration.py # Integration tests
├── test_edge_cases.py # Edge case tests
└── conftest.py # Shared fixtures
Python Code Standards
Package Manager
Always use uv instead of npm, pip, or ts-node.
# ✅ Correct
uv run pytest
uv run python script.py
uv add package-name
uv sync
# ❌ Wrong
pip install package-name
python script.py
npm install
Code Quality Tools
Ruff for linting and formatting:
# Check code
uv run ruff check .
# Fix issues automatically
uv run ruff check --fix .
# Format code
uv run ruff format .
# Check formatting without changes
uv run ruff format --check .
Type Hints
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 · 238 lines · 1,154 tokens per session scan A 12adf9cf9bd8
python-testing is a cursor rule published in the GitHub repository quinnjr/fruityloops-mcp (5 stars, last pushed 8mo ago), licensed MIT. It adds 1,154 tokens to every session, about $0.0058 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.
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.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.