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 rijuvashisht/Magneto --skill plan-ceo-reviewgit clone --depth 1 https://github.com/rijuvashisht/MagnetoWrote 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/rijuvashisht/magneto/plan-ceo-review)<a href="https://agentmods.dev/skills/rijuvashisht/magneto/plan-ceo-review"><img src="https://agentmods.dev/badge/skills/rijuvashisht/magneto/plan-ceo-review/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/rijuvashisht/magneto/plan-ceo-review"><img src="https://agentmods.dev/badge/skills/rijuvashisht/magneto/plan-ceo-review.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.00459 |
| Opus 5 | $0.00000 | $0.00230 |
| Sonnet 5 | $0.00000 | $0.00092 |
| Haiku 4.5 | $0.00000 | $0.00046 |
Grade A, and why
plan-ceo-review 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.
What it actually says
/plan-ceo-review — CEO Scope Challenge
Role: CEO / Founder
Inputs: plan.md
Outputs: appends to plan-reviews.md
Audit actions: plan-ceo-review.scored, plan-ceo-review.recommended
What This Skill Does
Reviews the plan from a product/founder perspective. 4 scope modes:
- EXPANSION — the plan is too small; there's a 10x product hiding inside
- SELECTIVE EXPANSION — add specific capabilities, hold others
- HOLD SCOPE — plan is right-sized, proceed
- REDUCTION — plan is over-scoped; cut it down to the wedge
The Protocol
Step 1: Read plan.md and design.md
Identify:
- What the narrow wedge is (from design.md)
- What the plan adds beyond the wedge
- Where the plan might be missing the real product
Step 2: Score the plan
| Dimension | 0-10 | Rationale |
|---|---|---|
| Wedge fidelity | Does the plan ship the wedge? | |
| Vision coverage | Does it leave room for the full vision? | |
| Scope discipline | Is anything here that shouldn't be? | |
| User impact | Will users notice / care? | |
| Timeline realism | Can this ship when promised? |
Step 3: Pick a mode and recommend
Write to plan-reviews.md:
## CEO Review
**Mode:** EXPANSION | SELECTIVE | HOLD | REDUCTION
**Scores:** wedge=N/10, vision=N/10, scope=N/10, impact=N/10, timeline=N/10
### Recommendation
<1 paragraph>
### Specific changes
- KEEP: <things>
- CUT: <things>
- ADD: <things>
- DEFER to Phase 2: <things>
Emit audit: magneto audit add plan-ceo-review.scored --payload '{"mode":"...","avgScore":N}'.
Trigger Phrases
- "ceo review"
- "founder review"
- "rethink scope"
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 · 62 lines · 0 tokens per session scan A 733b38faafa6
plan-ceo-review is a skill published in the GitHub repository rijuvashisht/Magneto (6 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 459 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-31.
Other skills, from other repositories
gh-issues
Fetch GitHub issues, spawn sub-agents to implement fixes and open PRs, then monitor and address PR review comments. Usage: /gh-issues [owner/repo] [--label bug] [--limit 5] [--milestone v1.0] [--assignee @me] [--fork user/repo] [--watch] [--interval 5] [--reviews-only] [--cron] [--dry-run] [--model glm-5]…
speckit-plan
Execute the implementation planning workflow using the plan template to generate design artifacts.
linear-app-setup
Create and configure a Linear agent app so the assistant can manage issues, projects, and workflows under its own identity.
run-task
Execute a single Todo task through In Progress to Review, meeting every acceptance criterion with tests and vibe-lint checks. Refuses Planning-status tasks. Invoked as /agiflow:run-task . Uses gettask, updatetask, createtaskcomment.
agent-phase-closeout
A Chinese-language process for closing out a completed work stage and recording its state. It summarizes finished work, preserves decisions, freezes completed interfaces, and writes a resume checkpoint.
orchestrate
Pipeline orchestration: dispatch the highest-priority ready tasks/work units to agents, manage capacity, and coordinate the Todo to Done flow. Invoked as /agiflow:orchestrate. Uses listtasks, listactivetasksbyorg, listmembers, updatetask, getworkunitprogress.