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 designgit 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/design)<a href="https://agentmods.dev/skills/jneaimi/evaluate-before-you-build/design"><img src="https://agentmods.dev/badge/skills/jneaimi/evaluate-before-you-build/design/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/design"><img src="https://agentmods.dev/badge/skills/jneaimi/evaluate-before-you-build/design.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.00099 | $0.03470 |
| Opus 5 | $0.00049 | $0.01735 |
| Sonnet 5 | $0.00020 | $0.00694 |
| Haiku 4.5 | $0.00010 | $0.00347 |
Grade A, and why
design 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 8d 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 — 409 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Solution Design Checkpoint (/design)
A solution architect's checkpoint. Before code gets written, shape the solution: boundaries, components, data flow, tradeoffs, failure modes. The deliverable is a solution design document, not working code.
Core principle: Options without honest tradeoffs are just preferences. Never produce a "chosen approach" until two or more real alternatives have been written down and compared against named non-functional requirements.
Interaction model: Scan-first like /prebuild (context matters for
architecture), then evaluate with AskUserQuestion options like /think.
This is the bridge skill: it sits between strategy (/think), planning
(/plan), and implementation (/prebuild).
How It Differs from the Others
| /design | /think | /plan | /prebuild | |
|---|---|---|---|---|
| Focus | Solution shape / architecture | Strategic decision | Delivery / timeline | Code generation |
| Output | ADR / design doc | Domain-adapted doc | Phased plan | Working code |
| Key work | Options + tradeoffs + NFRs | Evaluate + research | Sequence + own | Scan + build |
| Scans code? | Yes (context for options) | Sometimes | Sometimes | Yes |
Use /design after /think has confirmed why, and before /prebuild
generates code. On small features, skip straight to /prebuild. On
anything non-trivial or multi-component, design first.
Framework Reference
┌─────────────────────────────────────────┐
│ Level 5: Evaluate HUMAN → AI │ Problem, NFRs, chosen option
│ Level 4: Analyze HUMAN ↔ AI │ Options + tradeoffs (core)
├─────────────────────────────────────────┤
│ Level 3: Apply AI → HUMAN │ Produce design doc
│ Level 2: Understand AI → HUMAN │ Walk through the design
│ Level 1: Remember AI alone │ Save as ADR
└─────────────────────────────────────────┘
Commands
/design [topic] — Start design session
Begin a new solution design for the described problem.
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.
- 8d ago First seen · 409 lines · 99 tokens per session scan A b33cc6e68fbc
design is a skill published in the GitHub repository jneaimi/evaluate-before-you-build (2 stars, last pushed 4mo ago), licensed MIT. It adds 99 tokens to every session and 3,470 once invoked, about $0.0005 per session on Opus 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
frontend-design-director
Set subject-grounded visual direction for standard or deep UI work, redesign, polish, critique, anti-template review, or design handoff. Skip technical micro-fixes and isolated code edits.
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…
frontend-design-intelligence
Ground standard or deep UI work in product category, page pattern, design dials, domain UX risks, and anti-patterns before visual direction. Produces a brief, not code or tool setup.
frontend-layout-implementer
Implement an approved Design Implementation Spec or screenshot-derived spec in React/Next.js using existing CSS Modules, Redux, TanStack, and Axios conventions. Excludes unrelated stacks, live design tools, and new styling systems.
design-screenshot-spec
Turn user-supplied screenshots, copied inspect values, exports, assets, or design notes into a strict frontend Design Implementation Spec. Live design links alone are insufficient.
ios-accessibility-validator
Use this skill to audit iOS apps for accessibility compliance with Apple Human Interface Guidelines, WCAG 2.2 standards, and iOS accessibility best practices.