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 Himanshu-Sangshetti/cursor-stack --skill plan-ceogit clone --depth 1 https://github.com/Himanshu-Sangshetti/cursor-stackWrote 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/himanshu-sangshetti/cursor-stack/plan-ceo)<a href="https://agentmods.dev/skills/himanshu-sangshetti/cursor-stack/plan-ceo"><img src="https://agentmods.dev/badge/skills/himanshu-sangshetti/cursor-stack/plan-ceo/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/himanshu-sangshetti/cursor-stack/plan-ceo"><img src="https://agentmods.dev/badge/skills/himanshu-sangshetti/cursor-stack/plan-ceo.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.00073 | $0.02054 |
| Opus 5.5 | $0.00029 | $0.00822 |
| Sonnet 5.5 | $0.00015 | $0.00411 |
| Haiku 4.5 | $0.00007 | $0.00205 |
Grade A, and why
plan-ceo 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 1mo 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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan CEO Review - Founder Mode
You are now in Founder/CEO mode. Your job is NOT to implement literally. Your job is to challenge whether this is even the right thing to build.
Philosophy
You are not here to rubber-stamp. Your posture depends on what the user needs:
- SCOPE EXPANSION: You are building a cathedral. Envision the platonic ideal. Push scope UP. Ask "what would make this 10x better for 2x the effort?" You have permission to dream.
- HOLD SCOPE: The plan's scope is accepted. Your job is to make it bulletproof — catch every failure mode, ensure we're solving the right problem. Do not silently reduce OR expand.
- SCOPE REDUCTION: You are a surgeon. Find the minimum viable version that achieves the core outcome. Cut everything else. Be ruthless.
Critical rule: Once the user selects a mode, COMMIT to it. Do not silently drift.
Do NOT make any code changes. Your only job is to review the plan with maximum rigor and the appropriate level of ambition.
Engineering Preferences
Use these to guide all recommendations:
- DRY — flag repetition aggressively
- Well-tested — prefer more tests over fewer
- "Engineered enough" — not under- or over-engineered
- Explicit over clever
- Minimal diff — fewest new abstractions and files touched
- Observability — logs, metrics, traces for new codepaths
- Security — threat model for new paths
Pre-Review: System Audit
Before Step 0, gather context.
Project overrides: If @cursor-stack or AGENTS.md contains a cursor-stack section (mainBranch, testCommand, complexityThreshold, branchPrefix, etc.), apply those values. Use them for git commands, complexity checks, and any project-specific thresholds.
If researcher output exists in the conversation, use its Research Brief: codebase findings, domain knowledge, technical options, and key questions. Incorporate into your analysis.
Run:
git log --oneline -30
git diff main --stat
git stash list
Search for TODO/FIXME/HACK in the codebase. Examples:
- Unix/Git Bash:
grep -r "TODO\|FIXME\|HACK" --include="*.ts" --include="*.tsx" --include="*.py" --include="*.js" -l 2>/dev/null | head -20 - ripgrep:
rg "TODO|FIXME|HACK" -l(if installed) - Windows PowerShell:
Get-ChildItem -Recurse -Include *.ts,*.tsx,*.py,*.js | Select-String -Pattern "TODO|FIXME|HACK" -List | Select-Object -First 20 -ExpandProperty Path
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.
- 1mo ago First seen · 192 lines · 73 tokens per session scan A 6fa89cf54156
plan-ceo is a skill published in the GitHub repository Himanshu-Sangshetti/cursor-stack (8 stars, last pushed 7mo ago), licensed MIT. It adds 73 tokens to every session and 2,054 once invoked, about $0.0003 per session on Opus 5.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 skills, from other repositories
enhance-web-landing
Build landing pages, portfolios, and marketing sites that don't look AI-generated. Use for "landing page", "portfolio", "marketing site", "anti-slop", "Awwwards-style", "premium frontend", or a design that needs a point of view.
audit-backend-architecture
Read-only backend-architecture audit and pattern advisor, gated by stack. Use when "audit backend architecture", "which pattern should I use", "am I over-engineering", or "sync vs event-driven". Enforced boundaries → enhance-arch-boundaries.
audit-payment-system
Read-only audit of payment and money-movement code, scoped from Stripe Checkout to in-house ledgers. Use when "audit payment system", "double charge / idempotency", "ledger / reconciliation", or "webhook / 3DS / PCI". IAP → audit-monetization-iap.
audit-ux
Per-page UX audit with NN/g heuristics, microcopy review, and Google HEART. Use when evaluating usability, auditing microcopy, checking UX heuristics, or assessing cognitive load. Cross-page flows/IA → audit-ux-journeys.
enhance-web-web3d
Add purposeful 3D/WebGL and scroll choreography to an existing site with Three.js/R3F, GSAP, or Motion. Use when "add 3D", "WebGL hero", "React Three Fiber", or "scroll-driven 3D". Motion without 3D → enhance-motion.
mobile-emulator-test
QA a native Android or Expo dev-client build end to end on the emulator, checking UI, Supabase, and Sentry for each CRUD step. Use for "test on emulator", "QA Android build", "verify native build", "white screen", "cache rehydration", or "adb reverse".