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.
git clone --depth 1 https://github.com/ekakit/lightfast-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/ekakit/lightfast-mcp/development-workflow)<a href="https://agentmods.dev/rules/ekakit/lightfast-mcp/development-workflow"><img src="https://agentmods.dev/badge/rules/ekakit/lightfast-mcp/development-workflow/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/ekakit/lightfast-mcp/development-workflow"><img src="https://agentmods.dev/badge/rules/ekakit/lightfast-mcp/development-workflow.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00412 | $0.00412 |
| Opus 5.5 | $0.00165 | $0.00165 |
| Sonnet 5.5 | $0.00082 | $0.00082 |
| Haiku 4.5 | $0.00041 | $0.00041 |
Grade A, and why
development-workflow 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 2mo 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.
What it actually says
Development Workflow
Tool Stack
- Use
uvfor dependency management and running commands - Use
taskipyfor common development tasks - Use
noxfor comprehensive testing across Python versions - Use
rufffor linting and formatting
Common Commands
Setup & Development
# Setup
uv sync --extra dev
# Development
uv run task lint # Run linting
uv run task format # Format code
uv run task test_fast # Quick tests
uv run task demo # Test working system
Server Management
uv run lightfast-mcp-orchestrator init # Create sample config
uv run lightfast-mcp-orchestrator list # List available servers
uv run lightfast-mcp-orchestrator start # Start servers interactively
uv run lightfast-mcp-orchestrator ai # Start AI client
# Individual Servers
uv run lightfast-blender-server # Start Blender server directly
uv run lightfast-mock-server # Start mock server directly
Testing Commands
# Fast feedback
nox -s test_fast # Fast tests (excluding slow)
# Full test suite
nox
# Specific test types
nox -s test_e2e # End-to-end tests
nox -s test_integration # Integration tests
nox -s test_coverage # Tests with coverage
nox -s test-3.13 # Python 3.13 tests
nox -s typecheck # MyPy type checking
nox -s verify_system # System verification
Development Guidelines
- Use async/await patterns throughout for better performance
- Prefer configuration over hardcoded values
- Include appropriate tests for new functionality
- Follow the existing project patterns and conventions
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.
- 2mo ago First seen · 63 lines · 412 tokens per session scan A 007261702b8f
development-workflow is a cursor rule published in the GitHub repository ekakit/lightfast-mcp (2 stars, last pushed 1y ago), licensed MIT. It adds 412 tokens to every session, about $0.0016 per session on Opus 5.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
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.
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.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.