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/boparaiamrit/skills-by-amritWrote 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/boparaiamrit/skills-by-amrit/planning-workflow)<a href="https://agentmods.dev/rules/boparaiamrit/skills-by-amrit/planning-workflow"><img src="https://agentmods.dev/badge/rules/boparaiamrit/skills-by-amrit/planning-workflow/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/boparaiamrit/skills-by-amrit/planning-workflow"><img src="https://agentmods.dev/badge/rules/boparaiamrit/skills-by-amrit/planning-workflow.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.00497 |
| Opus 5 | $0.00007 | $0.00249 |
| Sonnet 5 | $0.00003 | $0.00099 |
| Haiku 4.5 | $0.00001 | $0.00050 |
Grade A, and why
planning-workflow 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 9d 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 & Implementation Workflow
When implementing a feature or making a significant change, follow this structured workflow:
Phase 1: Research (Before Writing Code)
- Map the affected area — Find all files related to the change
- Understand patterns — How does existing code handle similar cases?
- Identify dependencies — What imports/exports are involved?
- Check tests — What existing tests cover this area?
- Read recent history — What changed recently? (
git log --oneline -15)
Phase 2: Plan
- List all files that need to be created or modified
- Define the changes for each file (specific, not vague)
- Identify edge cases — Null values, empty arrays, max values, concurrent access
- Estimate risk — What could go wrong?
- Define verification — How will we know this works?
Phase 3: Implement
- One file at a time — Complete each file before moving to the next
- Match patterns — Follow existing codebase conventions
- Verify incrementally — Check that each change compiles
- Write tests alongside code — Don't save all tests for the end
Phase 4: Verify
- Build passes —
npm run build - All tests pass —
npm test(not just new tests) - Lint passes —
npm run lint - Types pass —
npx tsc --noEmit - No regressions — Existing features still work
Phase 5: Review
- Self-review the diff — Read your own changes critically
- Check for code smells — God functions, duplicate logic, magic numbers
- Verify completeness — Did you address ALL requirements?
- Check security — Input validation, auth checks, data exposure
Project State
If a .planning/ directory exists:
- Read
STATE.mdfor current context - Update
STATE.mdafter completing work - Save plans to
.planning/plans/ - Save research to
.planning/research/
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.
- 9d ago First seen · 50 lines · 14 tokens per session scan A 0b9fc704c2cc
planning-workflow is a cursor rule published in the GitHub repository boparaiamrit/skills-by-amrit (5 stars, last pushed 5mo ago), licensed MIT. It adds 14 tokens to every session and 497 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-08-31.
Other cursor rules, from other repositories
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-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.