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-executiongit 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.00702 | $0.00702 |
| Opus 5 | $0.00351 | $0.00351 |
| Sonnet 5 | $0.00140 | $0.00140 |
| Haiku 4.5 | $0.00070 | $0.00070 |
Grade A, and why
command-execution 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- command-execution โ 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing โ 130 lines โ stays where its author put it; the contents beside it link to each section on GitHub.
COMMAND EXECUTION PROTOCOL
TL;DR: Execute commands ONE AT A TIME. Document each command's purpose, the command itself, and its result (success OR failure).
๐ซ PROHIBITED PATTERNS
Never use these command patterns:
โ COMMAND CHAINING - DO NOT USE:
cd todo-app && npm install
โ IMPLICIT CHAINING (NESTED DIRS) - DO NOT USE:
mkdir -p src/components/TodoList
โ MULTIPLE FILE OPERATIONS - DO NOT USE:
touch index.js style.css app.js
โ MULTIPLE PACKAGE INSTALLS - DO NOT USE:
npm install react react-dom react-router-dom
cd todo-app && npm install # DON'T do this - will crash terminal
โ CORRECT PATTERNS
โ CORRECT: Separate navigation and installation
cd todo-app
npm install
โ CORRECT: Using tool-based directory creation
Instead of mkdir commands, prefer using built-in tools:
Use list_dir tool to check existing directories Use edit_file tool to create files in new directories
For example, creating a component structure:
- Use relative paths when working with tools
- Create parent directories first, then child directories
- Create files within directories as neededdc. The edit prioritizes the built-in tools while maintaining the principle of creating one directory at a time to avoid terminal crashes.
โ CORRECT: One file at a time
touch index.js
touch style.css
touch app.js
โ CORRECT: One package at a time
npm install react
npm install react-dom
npm install react-router-dom
๐ COMMAND DOCUMENTATION FORMAT
Document EVERY command using this format:
### Command: [Brief Description]
Purpose: [Explain what this command will do]
```bash
[actual command]
Result: [What happened after execution] Next step: [What follows this command]
## ๐ FAILED COMMAND DOCUMENTATION FORMAT
When a command fails, document it using this format:
Command: [Brief Description]
Purpose: [Explain what this command will do]
[attempted command]
Result: FAILED Error message: [Error details]
Alternative Approach
[alternative command]
Resolution: [How the issue was resolved] Next step: [What follows this command]
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 ยท 130 lines ยท 702 tokens per session scan A d1eb1ade69ee
command-execution is a cursor rule published in the GitHub repository kfnzero/mantis-mcp-server (10 stars, last pushed 12mo ago), licensed MIT. It adds 702 tokens to every session, about $0.0035 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.