Borrowing it
Nothing to install: this file belongs to Cratis/VerticalSlices. 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/Cratis/VerticalSlices/main/.ai/skills/stepper-command-dialog/SKILL.mdgit clone --depth 1 https://github.com/Cratis/VerticalSlicesWrote 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/cratis/verticalslices/stepper-command-dialog)<a href="https://agentmods.dev/skills/cratis/verticalslices/stepper-command-dialog"><img src="https://agentmods.dev/badge/skills/cratis/verticalslices/stepper-command-dialog/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/cratis/verticalslices/stepper-command-dialog"><img src="https://agentmods.dev/badge/skills/cratis/verticalslices/stepper-command-dialog.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.00072 | $0.01905 |
| Opus 5.5 | $0.00029 | $0.00762 |
| Sonnet 5.5 | $0.00014 | $0.00381 |
| Haiku 4.5 | $0.00007 | $0.00191 |
Grade A, and why
stepper-command-dialog 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 1mo 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.
This is a copy
100% identical to stepper-command-dialog — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 234 lines — stays where its author put it; the contents beside it link to each section on GitHub.
StepperCommandDialog — Wizard Dialogs
StepperCommandDialog organizes a single command form across multiple named steps. Users navigate with Previous and Next buttons; Submit only appears on the last step when every field across all steps is valid.
Use this instead of CommandDialog when:
- The form has too many fields to show at once
- Fields can be grouped into logical stages (e.g. "Contact Info → Project Details → Summary")
- You want guided, linear input with per-step validation feedback
- The operation feels like a wizard or an onboarding flow
Step 1 — Define the command
A single command collects all fields across all steps. Each step contributes properties to the same command instance.
// Projects/CreateProject/CreateProject.cs — the slice file
[Command]
public record CreateProject(ProjectName Name, EmailAddress Email, Description Description, Money Budget)
{
public ProjectCreated Handle() => new(Name, Email, Description, Budget);
}
Run a Debug dotnet build to generate the CreateProject TypeScript proxy before importing it.
Step 2 — Build the dialog component
import { StepperCommandDialog } from '@cratis/components/CommandDialog';
import { StepperPanel } from '@cratis/components/CommandDialog';
import { InputTextField, TextAreaField, NumberField } from '@cratis/components/CommandForm/fields';
import { DialogResult, useDialogContext } from '@cratis/arc.react/dialogs';
import { CreateProject } from '../api/Projects/CreateProject';
const CreateProjectDialog = () => {
const { closeDialog } = useDialogContext();
return (
<StepperCommandDialog<CreateProject>
command={CreateProject}
title="Create New Project"
okLabel="Create"
onConfirm={() => closeDialog(DialogResult.Ok)}
onCancel={() => closeDialog(DialogResult.Cancelled)}
>
<StepperPanel header="Contact Info">
<InputTextField<CreateProject>
value={c => c.email}
title="Contact Email"
placeholder="Enter contact email"
type="email"
/>
</StepperPanel>
<StepperPanel header="Project Details">
<InputTextField<CreateProject>
value={c => c.name}
title="Project Name"
placeholder="Enter project name"
/>
<TextAreaField<CreateProject>
value={c => c.description}
title="Description"
placeholder="Describe the project"
rows={4}
/>
</StepperPanel>
<StepperPanel header="Budget">
<NumberField<CreateProject>
value={c => c.budget}
title="Budget"
placeholder="Enter budget"
/>
</StepperPanel>
</StepperCommandDialog>
);
};
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.
- 1mo ago First seen · 234 lines · 72 tokens per session scan A 51316f774418
stepper-command-dialog is a skill published in the GitHub repository Cratis/VerticalSlices (2 stars, last pushed 1mo ago), licensed MIT. It adds 72 tokens to every session and 1,905 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to stepper-command-dialog, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
cratis-screenplay-command-surface
Write the write side of a Cratis Screenplay .play model — the command block and its identifier, reads, validate, authorize, produces, handler and concurrency clauses, plus event, constraint, policy, persona, concept, type and seed. Use when declaring or changing a command, an event shape, a validation or authorization…
cratis-screenplay-read-surface
Declare the read side of a Cratis Screenplay .play model — the readmodel shape, query with by/filter/scoped to/observable/performer, and screen at its three levels of detail, including the data/action contract that later component bindings, templates, forms, toolbars, routes and outlets consume. Use when adding or…
cratis-screenplay-ui-composition
Compose the user interface of a Cratis Screenplay .play model — layout and responsive arrangement, screen/dialog templates, component data-context bindings, exposed template configuration, command forms and columns, navigation contributions, application navigation regions (topbar/sidebar, module…
cratis-arc-authentication-authorization-and-identity
Wire authentication, authorization and identity in a Cratis Arc application — IProvideIdentityDetails and the /.cratis/me endpoint, Arc's [Authorize]/[Roles]/[AllowAnonymous] attributes and named policies, fallback baselines, observable-query emission guards, IAuthenticationHandler, the Microsoft Identity Platform…
cratis-arc-command-execution
Execute an existing Cratis Arc command from backend code through ICommandPipeline — the scopeless and scoped overloads, the typed generic Execute, the pre-flight Validate, validation severity filtering, and how to read CommandResult. Use when a reactor, background job, scheduled task, or backend service must run a…
cratis-arc-command
Define a Cratis Arc command — the [Command] record, its Handle() method and return shape, the optional Provide() step, and the generated TypeScript proxy. Use when adding a command, choosing what Handle() should return, deciding which values may reach the causation chain (including API keys and other credentials…