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/golid-ai/golidWrote 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/golid-ai/golid/planning-standards)<a href="https://agentmods.dev/rules/golid-ai/golid/planning-standards"><img src="https://agentmods.dev/badge/rules/golid-ai/golid/planning-standards.svg" alt="Measured on agentmods" 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.00000 | $0.00449 |
| Opus 5 | $0.00000 | $0.00225 |
| Sonnet 5 | $0.00000 | $0.00090 |
| Haiku 4.5 | $0.00000 | $0.00045 |
Grade A, and why
planning-standards 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 8d 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.
What it actually says
Planning Standards
Thesis: Plans should be short enough to execute and specific enough to prevent predictable mistakes.
Use this rule for every docs/plans/**/*.md edit. First identify the plan type:
- Feature/module: use
plan-feature. - Deploy/env/ops: use
plan-infra. - Docs/audit/refactor/experiment: use the closest workflow rule, or this rule alone.
Universal Checklist
- State
Risk tier:usingworkflow-routingwhen the plan will drive implementation; keep T0/T1 plans lightweight. - State the goal, non-goals, and default decisions.
- Verify current-state claims with file references for nontrivial plans.
- Verify schema claims (tables, columns, enum values, status strings) against current migrations and cite migration:line. Schema names you remember are often wrong; the cost of catching that during SQL authoring is hours, the cost of catching it during plan review is minutes.
- Organize work into slices with acceptance criteria.
- Name risks with concrete mitigations, not just warnings.
- Include a verification path and rollback/reset posture where relevant.
- Keep the plan proportional. Prefer 250-350 lines for infra/feature plans unless the scope truly needs more.
Avoid
- Forcing a feature template onto infra or docs work.
- Over-documenting obvious implementation details to hide unresolved decisions.
- Safety mechanisms that cost more than the failure mode they prevent.
- Placeholder follow-ups like "seed/test/docs later".
- Mismatched numbering between plan phases and execution slices.
- Asserting schema from memory. Grep the migrations for every table/column/enum the plan names; the wrong table name is a 30-minute discovery in execution that costs 30 seconds in planning.
Retro Hook
After executing a plan, capture one lesson that should change the next plan's shape. If every plan keeps the same structure regardless of execution feedback, the template is calcifying.
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.
- 8d ago First seen · 41 lines · 0 tokens per session scan A 6bd2a6e70d6f
planning-standards is a cursor rule published in the GitHub repository golid-ai/golid (40 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 449 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-30.
Other cursor rules, from other repositories
adapter-features
Database-specific features must be implemented in the specialized adapter only. Base adapters (postgres, mysql, etc.) must remain database-agnostic.
unit-tests-tdd
TDD required for behavior changes; ≥80% package coverage on touched packages; unit-test conventions.
integration-tests
Human-readable integration test requests; helpers vs httptest; suites/ vs per-DB placement.
state-management
Use the following stack. Do not introduce or recommend Redux or React Context for shared/global state.
backend
You are an expert in Go, Gin, Gorm, Gen, Cosy (https://cosy.uozi.org/) with a deep understanding of best practices and performance optimization techniques in these technologies.
core
Core token-efficiency and response discipline rules. Always active.