command-execution

command-execution is a cursor rule for Cursor from kfnzero/mantis-mcp-server. It costs 702 tokens per session, scanned A, original, MIT.

A command-execution rule defines how terminal commands must be run in a coding project. It requires one command at a time and lists command patterns that are not allowed.

In plain words
What is it for?
For guiding directory navigation, package installation, file creation, and other terminal-based development tasks.
Why use it?
It helps prevent accidental command chaining, unclear failures, and multiple file or package operations being mixed together.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit For guiding directory navigation, package installation, file creation, and other terminal-based development tasks.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/kfnzero/mantis-mcp-server/command-execution
Install

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.

Clone the repo
git clone --depth 1 https://github.com/kfnzero/mantis-mcp-server

Made for: Cursor.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for command-execution

README.md
[![agentmods](https://agentmods.dev/badge/rules/kfnzero/mantis-mcp-server/command-execution/github.svg)](https://agentmods.dev/rules/kfnzero/mantis-mcp-server/command-execution)
Your own site
<a href="https://agentmods.dev/rules/kfnzero/mantis-mcp-server/command-execution"><img src="https://agentmods.dev/badge/rules/kfnzero/mantis-mcp-server/command-execution/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for command-execution

Your own site · 80×15
<a href="https://agentmods.dev/rules/kfnzero/mantis-mcp-server/command-execution"><img src="https://agentmods.dev/badge/rules/kfnzero/mantis-mcp-server/command-execution.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 702 This file is loaded in full into every session.
When invoked 702 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00702 $0.00702
Opus 5.5 $0.00281 $0.00281
Sonnet 5.5 $0.00140 $0.00140
Haiku 4.5 $0.00070 $0.00070

Measured 1mo ago against content hash d1eb1ade69ee, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.cursor/rules/Core Implementation/command-execution.mdc · 130 lines

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:

  1. Use relative paths when working with tools
  2. Create parent directories first, then child directories
  3. 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]

Read the full file on GitHub · 130 lines

Changes

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.

  1. 1mo ago First seen · 130 lines · 702 tokens per session scan A d1eb1ade69ee

Subscribe to this mod's changes

command-execution is a cursor rule published in the GitHub repository kfnzero/mantis-mcp-server (12 stars, last pushed 1y ago), licensed MIT. It adds 702 tokens to every session, about $0.0028 per session on Opus 5.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.