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/phase2-results/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/phase2-results)<a href="https://agentmods.dev/skills/radekamirko/c.r.i.s.p/phase2-results"><img src="https://agentmods.dev/badge/skills/radekamirko/c.r.i.s.p/phase2-results/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/phase2-results"><img src="https://agentmods.dev/badge/skills/radekamirko/c.r.i.s.p/phase2-results.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.00077 | $0.02457 |
| Opus 5 | $0.00039 | $0.01229 |
| Sonnet 5 | $0.00015 | $0.00491 |
| Haiku 4.5 | $0.00008 | $0.00246 |
Grade A, and why
phase2-results 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.
How it starts
The opening of the file, as written. The whole thing — 218 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.
R — Results: Outcome Alignment
"We don't know if we succeeded unless we defined what success looks like before we started."
Project State
At the start of Phase R: read
docs/crisp-state.json. Checkphases.Cis complete. Usephases.C.oneSentence,phases.C.constraints, andproject.typefor context — do not re-read all Phase C docs from scratch.At the end of Phase R (before exit checklist): update
docs/crisp-state.json:
- Set
phases.currentto"I"- Add
"R"tophases.complete- Set
phases.R.completetotrue- Fill
phases.R.baseline,phases.R.successTarget,phases.R.hitlZones,phases.R.stakeholders- Add any unresolved items to
phases.R.openQuestions
Do not discuss solutions or architecture until this phase is complete.
Step 1: Stakeholder Register — Pre-fill, Elicit, Confirm
Do not open a blank register and ask "who are the stakeholders?" — you already have what you need to start.
Pre-fill from existing docs:
| Register section | Source |
|---|---|
| Primary users | docs/problem-statement.md — who the problem belongs to |
| Adjacent teams / employees | docs/problem-statement.md — business context, who touches the process |
| External users / customers | docs/value-proposition-canvas.md — customer profile (external projects) |
| Impact per stakeholder | docs/problem-statement.md — what changes for each group when the problem is solved |
| Human-in-the-loop zones | docs/problem-statement.md — constraints; docs/swot.md — threats (external) |
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 · 218 lines · 0 tokens per session scan A e892eee2386d
phase2-results is a skill published in the GitHub repository radekamirko/C.R.I.S.P (52 stars, last pushed 3mo ago), licensed MIT. It adds 77 tokens to every session and 2,457 once invoked, about $0.0004 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'.
procure-to-pay-advisor
Multi-jurisdiction procure-to-pay accounting reference covering PO matching, AP accruals, vendor management, and related compliance.
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…
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…
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…