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/ekakit/lightfast-mcp/mcp-configurationgit 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/mcp-configuration)<a href="https://agentmods.dev/rules/ekakit/lightfast-mcp/mcp-configuration"><img src="https://agentmods.dev/badge/rules/ekakit/lightfast-mcp/mcp-configuration.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.00011 | $0.02054 |
| Opus 5 | $0.00005 | $0.01027 |
| Sonnet 5 | $0.00002 | $0.00411 |
| Haiku 4.5 | $0.00001 | $0.00205 |
Grade A, and why
mcp-configuration 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 — 252 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Configuration Management
Overview
This rule applies when working with MCP (Model Context Protocol) configuration files, particularly .cursor/mcp.json and related server configuration.
File Patterns
.cursor/mcp.json.cursor/mcp_*.jsonconfig/servers.yaml- Files containing MCP server configurations
Upstream Repository Reference
Always reference the upstream repository for latest patterns and configurations:
- Repository:
lightfastai/lightfast-mcp - URL: https://github.com/lightfastai/lightfast-mcp
- Documentation: https://mcp.lightfast.ai
- Key Configuration Files:
.cursor/mcp.json: Local development MCP configuration.cursor/mcp_global_example.json: Global Cursor configuration templateconfig/servers.yaml: Server orchestration configurationpyproject.toml: Entry points and package structure
When to Fetch from Upstream
Always check the upstream repository when:
- Adding new MCP server configurations
- Updating existing server configurations
- Implementing new server types
- Troubleshooting configuration issues
- Looking for configuration best practices
- Understanding the latest server architecture patterns
GitHub Issues and PRs Interlink
Current Development Status
The upstream repository actively tracks development through GitHub Issues and Pull Requests:
🔄 Active Development Areas
- New Creative Applications: Issues for Photoshop (#1), OpenSCAD (#2), Maya (#28), Cinema 4D (#27)
- Feature Enhancements: OBJ import/export for Blender (#29), ongoing improvements
- Infrastructure: Dependency management via Renovate (#4), CI/CD optimizations
📋 Issue Categories
- Feature Requests: New MCP server implementations for creative applications
- Enhancement: Improvements to existing servers and functionality
- Dependencies: Automated dependency updates via Renovate bot
- Documentation: Roadmap and creative applications documentation
🔗 PR Workflow Patterns
- Feature Branches: Named as
jeevanpillay/{feature-name}orfeat/{application} - Automated PRs: Renovate bot handles dependency updates
- Draft PRs: Used for work-in-progress features (e.g., Photoshop MCP #3)
- Auto-generated Release Notes: CodeRabbit AI provides comprehensive PR summaries
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 · 252 lines · 11 tokens per session scan A cf58b0e4dbfc
mcp-configuration is a cursor rule published in the GitHub repository ekakit/lightfast-mcp (2 stars, last pushed 1y ago), licensed MIT. It adds 11 tokens to every session and 2,054 once invoked, about $0.0001 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.
family-instance-domain-actions
Family instance domain action implementation patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.