command-execution

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

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.

agentmods
npx agentmods add rules/kfnzero/mantis-mcp-server/command-execution
Clone the repo
git clone --depth 1 https://github.com/kfnzero/mantis-mcp-server

Made for: Cursor.

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. Scan, not verified.
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 $0.00702 $0.00702
Opus 5 $0.00351 $0.00351
Sonnet 5 $0.00140 $0.00140
Haiku 4.5 $0.00070 $0.00070

Measured yesterday against content hash d1eb1ade69ee, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 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.

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. yesterday 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 (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.