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.
npx skills add ratnesh-maurya/cursor-claude-personas --skill concise-planninggit clone --depth 1 https://github.com/ratnesh-maurya/cursor-claude-personasWrote 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/skills/ratnesh-maurya/cursor-claude-personas/concise-planning)<a href="https://agentmods.dev/skills/ratnesh-maurya/cursor-claude-personas/concise-planning"><img src="https://agentmods.dev/badge/skills/ratnesh-maurya/cursor-claude-personas/concise-planning/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/skills/ratnesh-maurya/cursor-claude-personas/concise-planning"><img src="https://agentmods.dev/badge/skills/ratnesh-maurya/cursor-claude-personas/concise-planning.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.00029 | $0.00386 |
| Opus 5 | $0.00015 | $0.00193 |
| Sonnet 5 | $0.00006 | $0.00077 |
| Haiku 4.5 | $0.00003 | $0.00039 |
Grade A, and why
concise-planning 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 11d 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.
This is a copy
97% identical to concise-planning — 1 line differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Concise Planning
Goal
Turn a user request into a single, actionable plan with atomic steps.
Workflow
1. Scan Context
- Read
README.md, docs, and relevant code files. - Identify constraints (language, frameworks, tests).
2. Minimal Interaction
- Ask at most 1–2 questions and only if truly blocking.
- Make reasonable assumptions for non-blocking unknowns.
3. Generate Plan
Use the following structure:
- Approach: 1-3 sentences on what and why.
- Scope: Bullet points for "In" and "Out".
- Action Items: A list of 6-10 atomic, ordered tasks (Verb-first).
- Validation: At least one item for testing.
Plan Template
# Plan
<High-level approach>
## Scope
- In:
- Out:
## Action Items
[ ] <Step 1: Discovery>
[ ] <Step 2: Implementation>
[ ] <Step 3: Implementation>
[ ] <Step 4: Validation/Testing>
[ ] <Step 5: Rollout/Commit>
## Open Questions
- <Question 1 (max 3)>
Checklist Guidelines
- Atomic: Each step should be a single logical unit of work.
- Verb-first: "Add...", "Refactor...", "Verify...".
- Concrete: Name specific files or modules when possible.
When to Use
This skill is applicable to execute the workflow or actions described in the overview.
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.
- 11d ago First seen · 69 lines · 29 tokens per session scan A a587e177f85e
concise-planning is a skill published in the GitHub repository ratnesh-maurya/cursor-claude-personas (8 stars, last pushed 5mo ago), licensed MIT. It adds 29 tokens to every session and 386 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to concise-planning, differing in 1 line, and is treated as a copy.
Other skills, from other repositories
requirements-authoring
To author, update, and validate functional/non-functional requirements as atomic units with user approval.
ijfw-plan
Use when the user says 'plan this', 'plan it', 'make a plan', 'let's plan', 'draft a plan', 'how should we tackle this', 'break this down', or invokes '/ijfw-plan'. Produces a falsifiable PLAN.md (software, book, campaign, design, research) with task breakdown, dependency wave-table, and success criteria — gated by…
hitl
Rosetta CRITICAL MUST skill to load as Prep Step 3 Step 2 — immediately after orchestrator-contract, right before loading any workflow. Loads the session-wide approval-gate protocol governing when to stop and wait vs proceed. WITHOUT IT decisions proceed silently, violating enterprise policy. Activate it for ALL tasks…
research
To run systematic deep research via meta-prompting — grounded references, incremental tracking, self-validation.
nextauth
NextAuth.js authentication for Next.js. Covers providers, sessions, and callbacks. Use for Next.js authentication. USE WHEN: user mentions "NextAuth", "Next.js auth", "Auth.js", asks about "Next.js authentication", "App Router auth", "next-auth", "authentication providers" DO NOT USE FOR: generic OAuth (use oauth2…
git-workflow
Git workflow best practices. Covers branching, commits, and collaboration. Use for version control guidance. USE WHEN: user mentions "git", "commit", "branch", "pull request", "PR", "merge", "rebase", "version control", asks about "commit message", "branching strategy", "git best practices", "conventional commits"…