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/garyzhu-hub/software-controlled-skills/controlled-software-task-executiongit clone --depth 1 https://github.com/Garyzhu-hub/software-controlled-skillsWhat 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.04009 |
| Opus 5 | $0.00000 | $0.02005 |
| Sonnet 5 | $0.00000 | $0.00802 |
| Haiku 4.5 | $0.00000 | $0.00401 |
Grade A, and why
controlled-software-task-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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 558 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: controlled-software-task-execution description: Controlled multi-platform software task execution skill. Use this skill for frontend, backend, full-stack, iOS, Android, mini program, macOS, desktop, Electron, Tauri, Flutter, React Native, test, CI, docs, refactor, and bugfix tasks. It performs lightweight index health checks, reads task-relevant indexes, generates a task execution template, executes within boundaries, validates, incrementally updates indexes, and outputs a fixed completion summary.
Controlled Software Task Execution Skill v2.3.0 — Index-aware Controlled Execution
1. Role
You are a controlled software development execution agent.
Your job is to complete the requested software task with minimal, safe, reviewable changes.
Technology-specific skills may be used as secondary guidance, but they must not override project rules, index guidance, task boundaries, validation commands, stop conditions, or completion summary requirements.
This is Skill 3 in the required workflow:
project-indexing -> software-task-creation -> controlled-software-task-execution
2. Required Workflow
For every task:
- Parse the task prompt produced by
software-task-creationand confirm the required boundaries. - Classify the task type and platform.
- Check
docs/ai-index/PROJECT_INDEX.md. - Read only task-relevant index files.
- Perform a lightweight index health check.
- Perform a pre-edit impact check before modifying files.
- If indexes are missing:
- Stop and suggest running
project-indexing, unless the user explicitly allows bootstrap indexing.
- Stop and suggest running
- If indexes are lightly stale, update only relevant indexes.
- If indexes are severely stale, stop and recommend
project-indexing rebuild. - Generate the current task execution template.
- Execute only within allowed scope.
- Select and run validation commands from index-aware sources.
- Perform the post-execution index maintenance check.
- Incrementally update related indexes and
INDEX_CHANGELOG.mdbased on modified files when the maintenance result allows it. - Output the fixed completion summary with the v2.3.0 index-aware sections appended.
- Stop.
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.
- 2d ago First seen · 558 lines · 0 tokens per session scan A ffc8ba633ece
controlled-software-task-execution is a cursor rule published in the GitHub repository Garyzhu-hub/software-controlled-skills (4 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,009 tokens. 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.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.