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/tech-documentationgit 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.00000 | $0.00888 |
| Opus 5 | $0.00000 | $0.00444 |
| Sonnet 5 | $0.00000 | $0.00178 |
| Haiku 4.5 | $0.00000 | $0.00089 |
Grade A, and why
tech-documentation 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical Documentation Guidelines
When creating or editing technical documentation, always reference the comprehensive developer guide:
@DEV.md
Documentation Consistency Rules
1. Architecture References
- Always reference DEV.md for architectural explanations
- Use consistent terminology from DEV.md (BaseServer, ServerConfig, etc.)
- Link to DEV.md sections rather than duplicating content
2. Code Examples
- Use patterns from DEV.md for code examples
- Reference actual implementation files mentioned in DEV.md
- Maintain consistency with DEV.md command examples
3. Setup Instructions
- Point to DEV.md Quick Start for setup procedures
- Use same command patterns as shown in DEV.md
- Reference DEV.md prerequisites section
4. Development Workflows
- Reference DEV.md workflows for development processes
- Use consistent task commands from DEV.md
- Point to DEV.md testing strategies
Documentation Validation Checklist
When editing technical documentation:
- Referenced @DEV.md for comprehensive information
- Used consistent terminology from DEV.md
- Commands match those in DEV.md
- Architecture descriptions align with DEV.md
- Examples follow DEV.md patterns
- No duplication of DEV.md content (link instead)
Quick Reference Commands
Always use these commands from DEV.md:
# Setup (from DEV.md Quick Start)
uv pip install -e ".[dev]"
uv run lightfast-mcp-orchestrator init
uv run lightfast-mcp-orchestrator start
# Development (from DEV.md Development Tasks)
uv run task lint
uv run task format
nox -s test_fast
# Testing (from DEV.md Testing section)
nox
uv run pytest tests/unit/ -v
Documentation Types
README Files
- Keep concise - link to DEV.md for details
- Use DEV.md Quick Start section for setup
- Reference DEV.md Architecture for technical details
API Documentation
- Follow DEV.md patterns for server implementation
- Use DEV.md examples as templates
- Reference DEV.md configurations
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 · 140 lines · 0 tokens per session scan A 1bec921db9f9
tech-documentation is a cursor rule published in the GitHub repository ekakit/lightfast-mcp (2 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 888 tokens. 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.