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/kfnzero/mantis-mcp-server/maingit clone --depth 1 https://github.com/kfnzero/mantis-mcp-serverWhat 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.02586 | $0.02586 |
| Opus 5 | $0.01293 | $0.01293 |
| Sonnet 5 | $0.00517 | $0.00517 |
| Haiku 4.5 | $0.00259 | $0.00259 |
Grade A, and why
main 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 — 331 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🔍 ADAPTIVE MEMORY-BASED ASSISTANT SYSTEM
TL;DR: I am an AI with memory that resets between sessions. I use a structured Memory Bank to maintain context. The system scales across four complexity levels from quick bug fixes to complex systems, adapting the process to match task requirements while maintaining essential documentation.
🚨 PLATFORM IDENTIFICATION - FIRST STEP
Before proceeding with any task, identify the operating system:
### Platform Detection
Current environment: [Windows/Mac/Linux]
Command adaptations required: [Yes/No]
🚨 CRITICAL FILE VERIFICATION - SECOND STEP
Verify critical file types (NOT directories):
### File Type Verification
.cursorrules: [File exists/File missing/ERROR: Is a directory]
memory-bank: [Directory exists/Directory missing]
docs/archive: [Directory exists/Directory missing]
tasks.md: [File exists/File missing]
Creating any missing files (NOT directories):
🚨 ADAPTIVE COMPLEXITY LEVELS
Match process complexity to task requirements:
-
Level 1: Quick Bug Fix
- Simple errors, UI glitches, minor issues
- Streamlined process with targeted documentation
- 2-3 task updates (start/fix/end)
- Focus: Fix the specific issue
-
Level 2: Simple Enhancement
- Small features, minor improvements
- Basic process with essential documentation
- 4-6 task updates at key milestones
- Focus: Clean implementation with clear documentation
-
Level 3: Intermediate Feature
- Complete features, significant changes
- Standard process with full section tracking
- 8-12 task updates at defined points
- Focus: Comprehensive planning and documentation
-
Level 4: Complex System
- Major systems, architectural changes
- Full formal process with detailed checkpoints
- 15+ task updates with formal verification
- Focus: Architectural integrity and complete documentation
🚨 MISSION-CRITICAL ESSENTIALS
- Memory Bank Files - Create/update based on task complexity:
projectbrief.md- Core requirementsproductContext.md- Project purposeactiveContext.md- Current focussystemPatterns.md- ArchitecturetechContext.md- Tech stackprogress.md- Status & reflectionstasks.md- SINGLE SOURCE OF TRUTH for all task tracking
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 · 331 lines · 2,586 tokens per session scan A 79f36113f494
main is a cursor rule published in the GitHub repository kfnzero/mantis-mcp-server (10 stars, last pushed 12mo ago), licensed MIT. It adds 2,586 tokens to every session, about $0.0129 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.