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 jneaimi/evaluate-before-you-build --skill plangit clone --depth 1 https://github.com/jneaimi/evaluate-before-you-buildWrote 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/jneaimi/evaluate-before-you-build/plan)<a href="https://agentmods.dev/skills/jneaimi/evaluate-before-you-build/plan"><img src="https://agentmods.dev/badge/skills/jneaimi/evaluate-before-you-build/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/skills/jneaimi/evaluate-before-you-build/plan"><img src="https://agentmods.dev/badge/skills/jneaimi/evaluate-before-you-build/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.00108 | $0.02780 |
| Opus 5.5 | $0.00043 | $0.01112 |
| Sonnet 5.5 | $0.00022 | $0.00556 |
| Haiku 4.5 | $0.00011 | $0.00278 |
Grade A, and why
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 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 — 340 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Planning Checkpoint (/plan)
A structured planning skill for product and project managers. Evaluates the initiative before committing to a roadmap — scope, stakeholders, constraints, dependencies, milestones, and risks. Output is a phased plan with clear owners and done-when criteria.
Core principle: A plan that wasn't evaluated isn't a plan — it's a wishlist. Never produce a roadmap until the human has answered the 6 planning questions.
Interaction model: Use AskUserQuestion for all decision points. The AI
proposes informed options (based on any available project context), the human
confirms or adjusts. Same Bloom ladder as /think — tuned for PM work.
How It Differs from /think and /prebuild
| /plan | /think | /prebuild | |
|---|---|---|---|
| Focus | Roadmap / execution plan | Any domain decision | Code generation |
| Deliverable | Phased plan + RACI + risk register | Domain-adapted doc | Working code |
| Lens | PM / delivery | Strategic / evaluative | Builder |
| Answers from | Human + AI-proposed options | Human provides substance | AI proposes, human picks |
| Duration | ~20 minutes | 30–60+ minutes | ~10 minutes |
Use /plan when the decision to do the thing is already made and you need
to sequence and scope the work. Use /think when you're still deciding whether
or why.
Framework Reference
┌─────────────────────────────────────────┐
│ Level 5: Evaluate HUMAN → AI │ Scope, owners, constraints
│ Level 4: Analyze HUMAN ↔ AI │ Dependencies, sequencing
├─────────────────────────────────────────┤
│ Level 3: Apply AI → HUMAN │ Produce the plan doc
│ Level 2: Understand AI → HUMAN │ Walk through the plan
│ Level 1: Remember AI alone │ Save to project tracking
└─────────────────────────────────────────┘
Commands
/plan [initiative] — Start planning
Begin a new planning session for the described initiative.
/plan continue — Resume
Resume from where a prior session left off.
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 · 340 lines · 108 tokens per session scan A 0e415387b067
plan is a skill published in the GitHub repository jneaimi/evaluate-before-you-build (2 stars, last pushed 6mo ago), licensed MIT. It adds 108 tokens to every session and 2,780 once invoked, about $0.0004 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
webdev-feedback
File WebDev bugs and ideas in GitHub with ownership, duplicate and privacy checks. Excludes fixes and automatic reporting.
think
Structured thinking skill implementing Bloom's AI Collaboration Framework v3. Auto-scales depth from stakes (reversibility + reliance): quick 3-question framing for reversible exploration, standard 6-question protocol for real decisions, deep mode with epistemics + teach-back + independent audit for binding one-way…
vibe-progress
Displays a live ASCII progress dashboard for the current vibe project. Triggers on "/vibe-progress", "progress:", "show progress", "how far along are we". Reads vibe/TASKS.md and git log to render a clean dashboard. Shows overall progress, phase gate status, active work, completed features, active bugs, backlog items…
process-mapper
Use when a BizOps lead, COO, or process-improvement owner needs to document an end-to-end business process (procurement, employee onboarding, incident handoff, customer-onboarding, claims adjudication) in BPMN-style notation, measure cycle times by stage, surface where work spends most of its time waiting vs. being…
strategic-alignment
Cascades strategy from boardroom to individual contributor. Detects and fixes misalignment between company goals and team execution. Covers strategy articulation, cascade mapping, orphan goal detection, silo identification, communication gap analysis, and realignment protocols. Use when teams are pulling in different…
moai-workflow-worktree
Git worktree management for parallel SPEC development with isolated workspaces, automatic branch registration, and seamless MoAI-ADK integration. Use when setting up parallel development environments.