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 autoplangit 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/autoplan)<a href="https://agentmods.dev/skills/rijuvashisht/magneto/autoplan"><img src="https://agentmods.dev/badge/skills/rijuvashisht/magneto/autoplan/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/autoplan"><img src="https://agentmods.dev/badge/skills/rijuvashisht/magneto/autoplan.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.00428 |
| Opus 5 | $0.00000 | $0.00214 |
| Sonnet 5 | $0.00000 | $0.00086 |
| Haiku 4.5 | $0.00000 | $0.00043 |
Grade A, and why
autoplan 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
/autoplan — Full Review Pipeline
Role: Review Pipeline
Inputs: plan.md
Outputs: plan-reviews.md with all reviews + test-plan.md
Audit actions: autoplan.started, autoplan.completed
What This Skill Does
Runs CEO → Eng → Design reviews automatically. Surfaces only taste decisions for user approval. Auto-detects which reviews apply based on plan content.
The Protocol
Step 1: Detect applicable reviews
Read plan.md. Decide which reviewers are needed:
- CEO: always (scope sanity)
- Eng: always if plan mentions architecture/API/schema/migration
- Design: only if plan mentions UI/UX/copy/component/screen
Step 2: Run reviewers in parallel
Invoke /plan-ceo-review, /plan-eng-review, /plan-design-review. Collect their outputs.
Step 3: Surface taste decisions
For each reviewer:
- [AUTO-APPLIED] changes → just report them
- [NEEDS-DECISION] changes → present to user via AskUserQuestion
Example:
3 taste decisions to make:
1. Scope mode (CEO): REDUCTION vs HOLD
CEO recommends: REDUCTION (cut the export feature)
Your call? [reduce / hold / expand]
2. Architecture (Eng): monolithic handler vs extracted service
Eng recommends: extract to authService to match community 12 pattern
Your call? [extract / inline]
3. Error UI (Design): toast vs inline banner
Design recommends: inline banner (consistent with src/errors/...)
Your call? [banner / toast]
Step 4: Apply decisions + write final plan
Update plan.md based on decisions. Write combined review to plan-reviews.md.
Emit audit: magneto audit add autoplan.completed --payload '{"reviewers":["..."],"decisions":N}'.
Trigger Phrases
- "autoplan"
- "full review"
- "review everything"
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 · 60 lines · 0 tokens per session scan A 3fcb3a1789c4
autoplan 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 428 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
expense-review-policy
Review invoices and contracts against accounts-payable policy before human approval.
skill-creator
Create, install, or update skills in the workspace. Use when (1) installing a skill from a URL or remote source, (2) creating a new skill from scratch, (3) updating or restructuring existing skills. Always use this skill for any skill installation or creation task.
image-generation
Generate or edit images from text prompts. Use when the user asks to create, draw, design, or edit an image, illustration, photo, icon, poster, or any visual content.
baby-sit
Monitor a GitHub pull request until CI is green, diagnose failures, and rerun only evidence-backed flaky GitHub Actions jobs.
continual-learning
Nightly refinement of an existing per-repo review-style prompt using this reviewer's own finding outcomes. Read confirmed (resolved-by-commit / thumbs-up) and dismissed (thumbs-down) findings, promote the bug patterns the team actually fixes, demote the false-positive patterns, reconcile against the current prompt…
peekaboo
Capture and automate macOS UI with the Peekaboo CLI.