Borrowing it
Nothing to install: this file belongs to radekamirko/C.R.I.S.P. 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/radekamirko/C.R.I.S.P/main/.claude/skills/phase4-spec/SKILL.mdgit clone --depth 1 https://github.com/radekamirko/C.R.I.S.PWrote 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/radekamirko/c.r.i.s.p/phase4-spec)<a href="https://agentmods.dev/skills/radekamirko/c.r.i.s.p/phase4-spec"><img src="https://agentmods.dev/badge/skills/radekamirko/c.r.i.s.p/phase4-spec/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/radekamirko/c.r.i.s.p/phase4-spec"><img src="https://agentmods.dev/badge/skills/radekamirko/c.r.i.s.p/phase4-spec.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.00114 | $0.10630 |
| Opus 5 | $0.00057 | $0.05315 |
| Sonnet 5 | $0.00023 | $0.02126 |
| Haiku 4.5 | $0.00011 | $0.01063 |
Grade A, and why
phase4-spec 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 10d 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 — 810 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pacing Rule — One Section at a Time
Present one section, deliverable, or elicitation move at a time. After presenting — stop. Wait for the client to respond. Do not pre-fill and present multiple sections in one message. Do not move to the next step until the client confirms, corrects, or gives a clear go-ahead.
The goal is a conversation, not a document dump. If you've written more than one section without a client response in between — you've gone too far.
S — Spec: Implementation Readiness
You are not building the thing. You are making the builder ready to build.
Project State
At the start of Phase S: read
docs/crisp-state.json. Check phases C, R, and I are complete. Useproject,phases.C,phases.R,phases.Ifields to orient before reading other docs. Pay attention to:project.agentInScope,project.memoryOwnershipRequired,phases.I.dataMappingRequired,phases.I.uxDiscoveryRequired.At the end of Phase S (before exit checklist): update
docs/crisp-state.json:
- Set
phases.currentto"P"- Add
"S"tophases.complete- Set
phases.S.completetotrue- Fill
phases.S.stack(harness, harnessOpen, memoryOwner, layers)- Fill
phases.S.mvpLine,phases.S.sprintCount,phases.S.sprints- Set
phases.S.analyticsRequiredandphases.S.landingPageRequired- Add any unresolved items to
phases.S.openQuestions
Output: a package a developer can read on Monday and start building on Tuesday.
Before You Start — Read These
All filled project documents live in docs/. Read from there, not from the blank /templates/ folder.
| File | What to extract |
|---|---|
docs/problem-statement.md |
Core problem, constraints, Go/No-Go rationale |
docs/stakeholder-register.md |
Who is impacted, what they need, human-in-the-loop zones |
docs/success-metrics.md |
Baseline measurements, success targets, second-order effects — used for MVP criteria and risk context |
docs/market-research.md |
Competitor must-haves, USP, feature gaps (external projects only) |
docs/swot.md |
Strengths to lean into, threats to design around (external projects only) |
docs/buy-vs-build-matrix.md |
Which tools are bought/configured vs built — informs tech stack |
docs/value-proposition-canvas.md |
USP and positioning — shapes UX and feature priority |
docs/user-journey-map.md |
Flows per user type — feeds UX spec directly |
docs/ux-discovery.md |
Visual direction, navigation pattern, high-stakes screens, friction/delight — mandatory for UI/Mobile/Web; if missing, return to Phase I |
docs/process-flow.md |
Step-by-step logic — feeds agent architecture |
docs/project-goals.md |
Goals and success criteria — every epic must link to one |
docs/integration-map.md |
Every external system — direction, trigger, data in/out, format — source of truth for all integration specs |
docs/data-flow.md |
Full system data pipe — confirmed by client in Phase I |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 810 lines · 0 tokens per session scan A a88e52ecdad7
phase4-spec is a skill published in the GitHub repository radekamirko/C.R.I.S.P (52 stars, last pushed 3mo ago), licensed MIT. It adds 114 tokens to every session and 10,630 once invoked, about $0.0006 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-30.
Other skills, from other repositories
janitor-discover
Find new skills on GitHub or check a specific skill before installing. Use when the user wants to search for skills, evaluate a skill URL, check overlap and security risk before installing, or compare a local skill against alternatives. Trigger with '/janitor-discover'.
alibaba-maestro
Alibaba Cloud Maestro routing skill. Classify the user's Alibaba Cloud task, select the narrowest specialist agent or the right team of specialists from the catalog, and dispatch them — single specialist for focused tasks, parallel team (max 4) for multi-domain tasks. Never auto-dispatch live-guard agents.…
azure-maestro
Use this skill to classify a user task, select the right Azure specialist agent or team of specialists from the catalog, and dispatch them. Single specialist for focused single-domain tasks; parallel team (max 4) for tasks that span multiple domains. Never auto-dispatches live-guard agents — those always pause for…
accounting-maestro
Route accounting questions to the narrowest specialist in the catalog. Use when you do not already know the specialist needed. Not for direct accounting answers; Maestro classifies, dispatches, and synthesizes only. Dispatches single agent for focused tasks, parallel team (max 3) for multi-domain tasks. Never…
model-registry-refresh
Re-verify and extend catalog/model-registry.json — the fail-closed model-name and reasoning-effort matrix scripts/model-policy.mjs validates against — via delegated Context7-backed research, orchestrator-owned registry edits, and the full validation chain; use when a policy check fails on an unregistered model, a…
add-educational-comments
Add educational comments to code files to transform them into effective learning resources. Explains the "why" behind syntax, idioms, and design choices, aligned with the learner's knowledge level and educational goals.