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/openplanr/OpenPlanrWrote 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/openplanr/openplanr/openplanr-operate)<a href="https://agentmods.dev/rules/openplanr/openplanr/openplanr-operate"><img src="https://agentmods.dev/badge/rules/openplanr/openplanr/openplanr-operate/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/openplanr/openplanr/openplanr-operate"><img src="https://agentmods.dev/badge/rules/openplanr/openplanr/openplanr-operate.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.00027 | $0.01740 |
| Opus 5 | $0.00014 | $0.00870 |
| Sonnet 5 | $0.00005 | $0.00348 |
| Haiku 4.5 | $0.00003 | $0.00174 |
Grade A, and why
openplanr-operate 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.
How it starts
The opening of the file, as written. The whole thing — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Operate
Run one useful operating review, not a ceremony. Build shared context once, fan out the five executive advisors, use the Challenger to test material claims, and let the Chair synthesize the result. Return a clean board report with decisions, actions, risks, gaps, and any real issues.
Scope the review
Infer these values from the request and repository when they are clear:
- Subject — the product, area, change, or decision under review.
- Window — a date or revision range, or the current snapshot when no comparison was requested.
- Requested decision — the choice the review should inform, or
periodic review. - Roster — all seven lenses unless the user selects fewer.
Use the current repository, current snapshot, periodic review, and all seven lenses as sensible
defaults. When ownership is useful, a recommendation may suggest a person, a role, or
unassigned.
Ask only when an unresolved choice would materially change the sources inspected or the decision being answered. Use the host's native structured-question UI when available, offering a recommended choice and short alternatives. Otherwise ask one concise chat question at a time. Never present the scope fields as a prose questionnaire.
Preserve the user's wording in cycle.md, followed by the effective scope used by the lenses.
Do not claim a trend from a current snapshot; describe current state and name any missing baseline.
Create the cycle workspace
Use a short subject slug and today's ISO date. Choose the first unused path;
when the base path exists, append -02, -03, and so on. Reuse an existing
cycle only when the user explicitly asks to resume it and its recorded scope
matches. Never overwrite a prior cycle implicitly.
.planr/operate/<date>-<slug>/
cycle.md
brief.md
<selected-lens-notes>.md
board-report.md
cycle.md records the effective scope, roster, repository revision when relevant, and the outcome
of each lens. If the directory is ignored by Git, continue locally and mention that in the report;
do not ask the user to change ignore rules. Report an exact filesystem error only when the cycle
workspace cannot be created or written.
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 · 175 lines · 27 tokens per session scan A 986fe3261846
openplanr-operate is a cursor rule published in the GitHub repository openplanr/OpenPlanr (4 stars, last pushed today), licensed MIT. It adds 27 tokens to every session and 1,740 once invoked, about $0.0001 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-09-16.
Other cursor rules, from other repositories
po
AIOX agent @po - Product Owner.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.