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/crisp-execute/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/crisp-execute)<a href="https://agentmods.dev/skills/radekamirko/c.r.i.s.p/crisp-execute"><img src="https://agentmods.dev/badge/skills/radekamirko/c.r.i.s.p/crisp-execute/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/crisp-execute"><img src="https://agentmods.dev/badge/skills/radekamirko/c.r.i.s.p/crisp-execute.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.00082 | $0.03336 |
| Opus 5 | $0.00041 | $0.01668 |
| Sonnet 5 | $0.00016 | $0.00667 |
| Haiku 4.5 | $0.00008 | $0.00334 |
Grade A, and why
crisp-execute 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 — 364 lines — stays where its author put it; the contents beside it link to each section on GitHub.
E — Execute: Build, Gate, Ship, Repeat
Spec is done. Now we build — one sprint at a time, with gates on the back end and a locked door on the front.
You are not Claude Code. You orchestrate Claude Code. You read the sprint spec, confirm the gate conditions, accept or reject change requests, run validation, and move to the next sprint. The build happens between your instructions — not in them.
Before You Start — Read These
| File | What to extract |
|---|---|
docs/sprint-plan.md |
Sprint sequence, features per sprint, dependencies |
docs/ai-spec-[sprint].md |
Acceptance criteria and locked scope for the current sprint |
docs/initial-backlog.md |
Full backlog with MVP tags — source of truth for what's in scope |
docs/risk-assessment.md |
Security and compliance risks relevant to this sprint |
CLAUDE.md |
Project context, NFRs, version rules, agent security rules |
crisp-state.json |
Current phase, sprint number, gate status, queued change requests |
If crisp-state.json does not exist, stop. Direct the user to run /crisp-start or /crisp-orchestrator — execution requires a completed spec.
If any Sprint AI Spec has unresolved open questions, stop. Return to Phase S and resolve them. A spec with open questions is not a spec.
The Execute Loop
Sprint N opens
→ Read sprint spec + acceptance criteria
→ Confirm pre-conditions (see 1A)
→ Claude Code builds
→ [mid-sprint: change requests hit intake gate]
→ Sprint N closes
→ Gate 1: Product validation (see 1B)
→ Gate 2: Security validation (see 1C)
→ Generate sprint delta doc (see 1D)
→ Generate progress report (see 1E)
→ Human validates and approves
→ If approved → update crisp-state.json → Sprint N+1
→ If rejected → fix loop (see 1F) → re-gate
1A: Sprint Pre-conditions
Before Claude Code writes a single line, verify:
- AI Spec for this sprint exists at
docs/ai-spec-sprint-[N].mdand is locked (no open questions) - All integration AI Specs for APIs used in this sprint are complete
- All dependency sprints are marked complete in
crisp-state.json - Security tooling is configured (Bearer in CI, see below)
- No change requests are pending from the previous sprint that affect this sprint's scope
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 · 364 lines · 0 tokens per session scan A 67d721cd04a7
crisp-execute is a skill published in the GitHub repository radekamirko/C.R.I.S.P (52 stars, last pushed 3mo ago), licensed MIT. It adds 82 tokens to every session and 3,336 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
salesforce-live-change-approval-protocol
Use this skill when any proposed mutation to a live Salesforce production org must be evaluated before execution. This is a refusal-by-default gate: if any required precondition is missing, the skill stops and refuses. Required preconditions are targetorgidentity, environmenttype, useridentity, permissionscope…
change-request-to-go-live-protocol
Use this skill when a Dynamics 365 change request must be structured and progressed through impact assessment, fit-gap analysis, UAT sign-off, go/no-go decision, go-live execution, and hypercare using the Success by Design framework. Defines the full change-to-go-live flow — change request intake, solution blueprint…
erp-crm-cutover-protocol
Use this skill when a Dynamics 365 ERP or CRM implementation is approaching go-live and must progress through mock migration, data reconciliation, cutover runbook execution, rollback testing, and the Success by Design go-live gate before production switchover. Orchestrates d365-data-migration-cutover-agent as primary…
incident-to-remediation-protocol
Use this skill when a security incident must be triaged, contained, remediated, and reviewed in a Zero Trust assume-breach posture across Microsoft 365 and Dynamics 365 environments. Defines the end-to-end flow from detection through severity triage, containment approval, investigation, remediation, and post-incident…
case-to-resolution-protocol
Use this skill when a customer service case must be triaged, routed to the right team, driven to resolution, and captured as reusable knowledge in Dynamics 365 Customer Service. Covers intake-to-routing, SLA tracking, escalation gates, knowledge capture, and post-resolution CSAT. Orchestrates the…
field-service-to-cash-protocol
Use this skill to orchestrate the field service to cash process (service to deliver) across Dynamics 365 Field Service and Dynamics 365 Finance, covering work order creation through service delivery, parts and inventory consumption, invoicing, and accounts receivable settlement. The skill defines stage gates, agent…