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/command-examplesgit 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.00021 | $0.01242 |
| Opus 5 | $0.00010 | $0.00621 |
| Sonnet 5 | $0.00004 | $0.00248 |
| Haiku 4.5 | $0.00002 | $0.00124 |
Grade A, and why
command-examples 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 — 224 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Command Documentation Examples
⚠️ CORRECT COMMAND DOCUMENTATION EXAMPLES ⚠️
Example 1: Basic Command Documentation
### Command: Create Component Directory
Purpose: Creating a directory for React components
```bash
mkdir src/components
Result: Successfully created components directory Next step: Create individual component files
🔄 TASK UPDATE: Create component directory structure - [X] Complete
- Updated in tasks.md ✓
🔄 IMPLEMENTATION UPDATE:
- Added to activeContext.md: Component directory structure created following React best practices
### Example 2: Failed Command With Alternative
Command: Install React Router Package
Purpose: Adding routing capability to the React application
npm install react-router
Result: FAILED Error message: npm ERR! 404 Not Found - GET https://registry.npmjs.org/react-router - Not found
Alternative Approach
npm install react-router-dom
Resolution: Successfully installed react-router-dom v6.8.1 Next step: Set up router configuration
🔄 TASK UPDATE: Install routing package - [X] Complete
- Updated in tasks.md ✓
🔄 IMPLEMENTATION UPDATE:
- Added to activeContext.md: Installed react-router-dom as the routing solution
### Example 3: Platform-Specific Command
Command: Create Empty Configuration File
Purpose: Creating a configuration file for the application
Platform considerations:
- Windows: Using echo.> command
- Mac/Linux: Using touch command
- Current platform: Windows
echo.> config.json
Result: Successfully created empty config.json file Next step: Add default configuration settings
🔄 TASK UPDATE: Create configuration file - [X] Complete
- Updated in tasks.md ✓
🔄 IMPLEMENTATION UPDATE:
- Added to activeContext.md: Empty configuration file created, will be populated with environment-specific settings
### Example 4: Multiple Step Command Sequence
Command: Create Project Directory
Purpose: Creating the main project directory
mkdir todo-app
Result: Successfully created todo-app directory Next step: Navigate to project directory
Command: Navigate to Project Directory
Purpose: Moving into the project directory to initialize the application
cd todo-app
Result: Successfully navigated to todo-app directory Next step: Initialize npm project
Command: Initialize NPM Project
Purpose: Setting up package.json for the project
npm init -y
Result: Successfully created package.json with default values Next step: Install core dependencies
🔄 TASK UPDATE: Set up project structure - [X] Complete
- Updated in tasks.md ✓
🔄 IMPLEMENTATION UPDATE:
- Added to activeContext.md: Project initialized with directory structure and package.json
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 · 224 lines · 1,242 tokens per session scan A f5654b1009b5
command-examples is a cursor rule published in the GitHub repository kfnzero/mantis-mcp-server (10 stars, last pushed 12mo ago), licensed MIT. It adds 21 tokens to every session and 1,242 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.
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.