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/moclam1905/cocktailrecipes/command-executiongit clone --depth 1 https://github.com/moclam1905/CocktailRecipesWhat 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.00000 | $0.02228 |
| Opus 5 | $0.00000 | $0.01114 |
| Sonnet 5 | $0.00000 | $0.00446 |
| Haiku 4.5 | $0.00000 | $0.00223 |
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 — 235 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 · 235 lines · 0 tokens per session scan A 3f88c33ce358
command-execution is a cursor rule published in the GitHub repository moclam1905/CocktailRecipes (1 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,228 tokens. 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
android-project
Core behavior rules for AI agents working on this Android project.
ios-project-bootstrap
Walks a developer through bootstrapping a BRAND-NEW iOS project for agentic CLI delivery — Apple Developer Program enrollment, App Store Connect listing, provisioning profiles, Fastlane setup from scratch, Firebase App Distribution, TestFlight + App Store first upload. Use when the user says they're starting a new iOS…
android-project-bootstrap
Walks a developer through bootstrapping a BRAND-NEW Android project for agentic CLI delivery — creating the Firebase project, registering the Android app, setting up App Distribution, creating the Google Play Console listing, wiring API access, and installing the Gradle plugins. Use when the user says they're starting…
android-project-onboarding
Walks a new developer through one-time setup of an EXISTING configured Android project from a blank macOS install — JDK, Android SDK, AVD, scrcpy, shell env vars, credential files, and a smoke-test build. Assumes Firebase project + Play Console listing already exist; user just needs to acquire credentials. Use when…
ios-project-onboarding
Walks a new developer through one-time setup of an EXISTING configured iOS project from a blank macOS install — Xcode, Fastlane, SPM dependencies, code signing, simulator, and a smoke-test build. Assumes App Store Connect + Firebase + Fastlane are already configured upstream; user just needs local toolchain +…
ios-project
Core behavior rules for AI agents working on this iOS project.