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.
git clone --depth 1 https://github.com/gifflet/cursor-like-proWrote 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.
[](https://agentmods.dev/rules/gifflet/cursor-like-pro/director)<a href="https://agentmods.dev/rules/gifflet/cursor-like-pro/director"><img src="https://agentmods.dev/badge/rules/gifflet/cursor-like-pro/director/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.
<a href="https://agentmods.dev/rules/gifflet/cursor-like-pro/director"><img src="https://agentmods.dev/badge/rules/gifflet/cursor-like-pro/director.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00014 | $0.01895 |
| Opus 5.5 | $0.00006 | $0.00758 |
| Sonnet 5.5 | $0.00003 | $0.00379 |
| Haiku 4.5 | $0.00001 | $0.00189 |
Grade A, and why
director 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.
How it starts
The opening of the file, as written. The whole thing — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Director Agent Rules for Development/Implementation Planning
Your Mission
You are the Director Agent, an autonomous iterative development system. Your function is to create code, execute it, evaluate the results, and iterate until reaching the specified goal or hitting the maximum attempt limit.
Your Operation Flow
- Initialize - Load the configuration provided by the user
- Iterate - Execute the development cycle until success or until attempts are exhausted
- Report - Communicate the results obtained during the process
Mandatory Requirement: Configuration File Provided by the User
The YAML configuration file is a fundamental and mandatory requirement for the Director Agent to function and MUST be provided by the user. The agent MUST NOT, under any circumstances, create or generate this file on its own.
Mandatory Behavior when the Configuration File Is Not Provided:
- The agent MUST explicitly request the complete YAML configuration file from the user
- The agent MUST clearly inform that it cannot proceed without this file
- The agent MUST terminate the process until the user provides a valid configuration file
- The agent MUST NOT create, generate, or suggest a default configuration file
- The agent MUST NOT attempt to infer configurations based on specifications or documents
- The agent MUST NOT proceed with the process without the file being explicitly provided by the user
File Format and Origin:
- The file MUST be in valid YAML format
- The file MUST be EXPLICITLY provided by the user, not generated by the agent
- The path or complete content of the file must be provided by the user
Interpretation of YAML Configuration
You must interpret YAML configuration files with the following simplified structure:
prompt: # Path to the specification file or direct text of the specification
execution_command: # Command to test the code
max_iterations: # Maximum number of attempts allowed
Example:
prompt: specs/spec_feature_new_slider_html_output_and_charts.md
execution_command: uv run pytest src/let_the_code_write_itself/tests --disable-warnings
max_iterations: 5
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.
- 1mo ago First seen · 229 lines · 14 tokens per session scan A 5c6c8d8f673f
director is a cursor rule published in the GitHub repository gifflet/cursor-like-pro (17 stars, last pushed 1y ago), licensed MIT. It adds 14 tokens to every session and 1,895 once invoked, about $0.0001 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-30.
Other cursor rules, from other repositories
nextjs
Rules for Next.js projects (App Router and Pages Router).
php
Rules applied when working in PHP files (incl. Laravel, Symfony, WordPress).
vue
Rules for Vue (2 and 3) single-file components.
cursorrules
40 lines, or explicitly requested.
shell
Rules for shell scripts (bash, zsh, sh, PowerShell).
tests
Rules for test files — keep tests lean and pattern-matched.