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/zenobia0000/cursor-agentic-coding-template/command-executiongit clone --depth 1 https://github.com/Zenobia0000/cursor-agentic-coding-templateWhat 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.00012 | $0.01237 |
| Opus 5 | $0.00006 | $0.00619 |
| Sonnet 5 | $0.00002 | $0.00247 |
| Haiku 4.5 | $0.00001 | $0.00124 |
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.
This is a copy
100% identical to command-execution — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
COMMAND EXECUTION SYSTEM
TL;DR: This system provides guidelines for efficient command execution, balancing clarity and token optimization through appropriate command chaining, with proper documentation of commands and results.
🔍 COMMAND EFFICIENCY WORKFLOW
graph TD
Start["Command<br>Planning"] --> Analyze["Analyze Command<br>Requirements"]
Analyze --> Balance["Balance Clarity<br>vs. Efficiency"]
Balance --> Complexity{"Command<br>Complexity?"}
Complexity -->|"Simple"| Single["Execute<br>Single Command"]
Complexity -->|"Moderate"| Chain["Use Efficient<br>Command Chaining"]
Complexity -->|"Complex"| Group["Group Into<br>Logical Steps"]
Single & Chain & Group --> Verify["Verify<br>Results"]
Verify --> Document["Document<br>Command & Result"]
Document --> Next["Next<br>Command"]
📋 COMMAND CHAINING GUIDELINES
graph TD
Command["Command<br>Execution"] --> ChainApprop{"Is Chaining<br>Appropriate?"}
ChainApprop -->|"Yes"| ChainTypes["Chain<br>Types"]
ChainApprop -->|"No"| SingleCmd["Use Single<br>Commands"]
ChainTypes --> Sequential["Sequential Operations<br>cmd1 && cmd2"]
ChainTypes --> Conditional["Conditional Operations<br>cmd1 || cmd2"]
ChainTypes --> Piping["Piping<br>cmd1 | cmd2"]
ChainTypes --> Grouping["Command Grouping<br>(cmd1; cmd2)"]
Sequential & Conditional & Piping & Grouping --> Doc["Document<br>Commands & Results"]
🚦 DIRECTORY VERIFICATION WORKFLOW
graph TD
Command["Command<br>Execution"] --> DirCheck["Check Current<br>Directory"]
DirCheck --> ProjectRoot{"In Project<br>Root?"}
ProjectRoot -->|"Yes"| Execute["Execute<br>Command"]
ProjectRoot -->|"No"| Locate["Locate<br>Project Root"]
Locate --> Found{"Project Root<br>Found?"}
Found -->|"Yes"| Navigate["Navigate to<br>Project Root"]
Found -->|"No"| Error["Error: Cannot<br>Find Project Root"]
Navigate --> Execute
Execute --> Verify["Verify<br>Results"]
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 · 129 lines · 12 tokens per session scan A fe7450063525
command-execution is a cursor rule published in the GitHub repository Zenobia0000/cursor-agentic-coding-template (5 stars, last pushed 4mo ago), licensed MIT. It adds 12 tokens to every session and 1,237 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to command-execution, differing in 0 lines, and is treated as a copy.
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.