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/rule-generationgit clone --depth 1 https://github.com/ekakit/lightfast-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.00011 | $0.00649 |
| Opus 5 | $0.00005 | $0.00324 |
| Sonnet 5 | $0.00002 | $0.00130 |
| Haiku 4.5 | $0.00001 | $0.00065 |
Grade A, and why
rule-generation 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rule Generation Workflow
Use this rule when developing new workflow patterns that should be captured as reusable Cursor rules.
When to Generate New Rules
Generate new rules when you discover:
- Repetitive Workflows: Actions you perform multiple times
- Context-Specific Patterns: File-type specific behaviors
- Quality Gates: Validation steps that should be automated
- Debugging Procedures: Common troubleshooting steps
- Integration Patterns: Multi-tool workflows
Rule Template for lightfast-mcp
Use this template structure for new rules:
@.cursor/rules/server-development-workflow.mdc
Follow this pattern, adapting the workflow steps for your specific use case.
Suggested Rule Categories
New Server Types
Create rules for new creative applications:
- TouchDesigner MCP development workflow
- Ableton Live MCP development workflow
- Unity/Unreal Engine MCP development workflow
Development Phases
Create rules for different development phases:
- Prototyping workflow (fast iteration, minimal validation)
- Production workflow (comprehensive checks)
- Debugging workflow (diagnostic commands, logging)
Integration Testing
Create rules for testing integrations:
- Multi-server workflow testing
- Cross-platform testing workflow
- Performance testing workflow
Rule Naming Convention
Use descriptive names that indicate:
- Context: When the rule applies
- Action: What workflow it provides
- Scope: How specific vs. general it is
Examples:
touchdesigner-development-workflow.mdcmulti-server-integration-testing.mdcperformance-optimization-workflow.mdcproduction-deployment-checklist.mdc
Rule File Organization
Organize rules by:
- Always Applied: Core concepts, architecture, security
- Auto-Attached: File-pattern based rules
- Manual: Specialized workflows triggered with
@rule-name
Testing New Rules
After creating a new rule:
- Test Auto-Attachment: Edit matching files to verify rule triggers
- Test Manual Activation: Use
@rule-nameto verify manual trigger - Validate Commands: Ensure all suggested commands work
- Check Conflicts: Verify rule doesn't conflict with existing rules
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 · 103 lines · 11 tokens per session scan A a441d34e8181
rule-generation 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 649 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.
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.