Borrowing it
Nothing to install: this file belongs to chacosoldier/compabob. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/chacosoldier/compabob/main/.claude/skills/design-precheck/SKILL.mdgit clone --depth 1 https://github.com/chacosoldier/compabobWrote 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/chacosoldier/compabob/design-precheck)<a href="https://agentmods.dev/skills/chacosoldier/compabob/design-precheck"><img src="https://agentmods.dev/badge/skills/chacosoldier/compabob/design-precheck/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/chacosoldier/compabob/design-precheck"><img src="https://agentmods.dev/badge/skills/chacosoldier/compabob/design-precheck.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.00139 | $0.01250 |
| Opus 5.5 | $0.00056 | $0.00500 |
| Sonnet 5.5 | $0.00028 | $0.00250 |
| Haiku 4.5 | $0.00014 | $0.00125 |
Grade A, and why
design-precheck 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 5d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Precheck
Kill or shrink a build while it is still a plan. The pre-mortem hook only checks the section's shape; this skill makes its content real. Never hand-type the section to get past the hook.
1. Find the plan
- In plan mode: the plan file Claude Code named under
~/.claude/plans/. - Otherwise: the file path or pasted text. Outside plan mode, return the section in chat and add it to the plan file once the work enters plan mode.
Note which hook triggers the plan fires (irreversible, wide blast radius, weeks of work); pass them to every advisor.
2. Close open decisions first (one round, at most four questions)
Advisors attacking a plan that rests on an unmade decision produce findings about the guess, not the plan. List the decisions the plan leaves open whose answer would change its shape: who uses the result, the data source, what done means, what is out of scope. If any exist and the user is present, ask them in ONE AskUserQuestion call, each with your recommended answer as the first option, and fold the answers in. Anything still open goes to the advisors as a stated assumption.
3. Fan out, in parallel, in ONE message
Give every advisor the plan text (and its path), the triggers it fired, and the common failure patterns below. Each returns at most five findings, one line each: SEVERITY (FATAL|HIGH|MED) | failure mode | concrete trigger | what to change in the plan, then a one-word verdict. Judgment only, no rewrites.
| Seat | Agent | Brief |
|---|---|---|
| Pre-mortem (mandatory) | strategy-advisor |
"Six months from now this plan failed. List the top failure modes and what we would wish we had done differently." Attack adoption and value: who uses it, which step depends on someone doing something by hand, what already covers it. |
| Mechanics | principal-engineer |
Read the files the plan names; cite file:line. Attack state (first run, re-runs, partial failure), anything that fails silently, untrusted input reaching a script or a model, sends or secrets. Skip this seat when the plan builds nothing technical. |
| Dissenter | skeptic (mode DISSENT) |
Assigned position: don't build this as specified. Argue that the smallest version, or something that already exists (name it), gets most of the value, and that the definition of done can pass while the goal fails. |
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.
- 5d ago First seen · 63 lines · 139 tokens per session scan A 88aec0fabfb2
design-precheck is a skill published in the GitHub repository chacosoldier/compabob (34 stars, last pushed 5d ago), licensed MIT. It adds 139 tokens to every session and 1,250 once invoked, about $0.0006 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-10-24.
Other skills, from other repositories
ha-logs
A read-only troubleshooting skill for querying Hope Agent’s local SQLite databases, which store logs, conversations, and background-job status.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
vellum-memory-v3-migration
One-time migration of an existing memory-v2 concept corpus into the memory-v3 section-grain "wiki" — topical articles with a stand-alone lead and queryable sections — with loss-proof staging, assistant-reviewed authoring, and a retrieval-eval gate before cutover.
media-processing
Ingest and process media files (video, audio, image).
notifications
Send notifications through the unified notification router.
visualize
Render a polished visual inline in the chat as part of your answer — a diagram, a chart, an interactive explainer, or a UI mockup. Load it proactively whenever an explanation would land better as a picture than as prose. Do not wait to be asked.