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/GktuOktay/ai-skillsWrote 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/gktuoktay/ai-skills/make-plan)<a href="https://agentmods.dev/rules/gktuoktay/ai-skills/make-plan"><img src="https://agentmods.dev/badge/rules/gktuoktay/ai-skills/make-plan/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/gktuoktay/ai-skills/make-plan"><img src="https://agentmods.dev/badge/rules/gktuoktay/ai-skills/make-plan.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.00000 | $0.01117 |
| Opus 5 | $0.00000 | $0.00558 |
| Sonnet 5 | $0.00000 | $0.00223 |
| Haiku 4.5 | $0.00000 | $0.00112 |
Grade A, and why
make-plan 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.
How it starts
The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Planning & Task Breakdown Skill
Overview
This skill focuses on taking a high-level requirement or abstract idea and transforming it into a structured, actionable, and prioritized implementation plan. It covers task decomposition, dependency mapping, risk identification, and structured outputs for engineering execution.
Phase 1: Requirements Analysis
Before breaking down tasks, establish absolute clarity on what needs to be built.
- Objective Statement: What is the primary goal of this project?
- Scope Boundaries: Explicitly define what is IN scope and what is OUT of scope.
- Success Criteria: How will we know this project is completed successfully? (e.g., Performance metrics, user acceptance tests).
Phase 2: Task Decomposition (The Hierarchy)
Break down the work into progressively smaller, manageable units.
- Epics (High-Level Features): Major functional areas (e.g., "User Authentication System").
- Stories (User-Centric Work): Specific functionality delivering value (e.g., "As a user, I can log in with Google").
- Tasks (Technical Implementation): Engineering steps to achieve a story (e.g., "Set up OAuth2 endpoints", "Create Login UI component").
- Subtasks (Checklist Items): Micro-steps (e.g., "Add Google logo asset", "Write unit tests for token validation").
Rule of Thumb: A Task should represent work that takes a single engineer 1-3 days to complete. If it takes longer, it should be broken down further.
Phase 3: Dependency Mapping
Identify the order of operations to prevent blockers.
- Finish-to-Start (FS): Task B cannot start until Task A finishes. (Most common in software).
- Parallel Workstreams: Identify which tasks can be developed concurrently by different team members (e.g., Frontend UI can be built with mock data while Backend API is being developed).
Example Mapping:
- Database Schema (Blocks ->) Backend API
- Backend API (Blocks ->) Frontend Integration
- UI Mockups (Blocks ->) Frontend Layout
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 · 100 lines · 1,117 tokens per session scan A d69500a81340
make-plan is a cursor rule published in the GitHub repository GktuOktay/ai-skills (2 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,117 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-09-03.
Other cursor rules, from other repositories
02-contributor-guide
Guidelines for contributing new rules or editing existing ones.
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.