cratis-components-stepper-command-dialog

cratis-components-stepper-command-dialog is a skill for Claude Code, Codex from Cratis/AI. It costs 95 tokens per session (2,067 once invoked), scanned A, original, MIT.

A React dialog that divides one Cratis Arc command form into several named steps. A wizard is a form completed in stages, with validation before the user can move forward or submit.

In plain words
What is it for?
Use it for multi-stage command forms, such as contact details followed by other grouped information, including pre-filled edit workflows.
Why use it?
It keeps a large form from showing every field at once and gives each stage focused feedback. All steps still contribute to the same command.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is import { CreateProject } from '../api/Projects/CreateProject';.

Good fit Use it for multi-stage command forms, such as contact details followed by other grouped information, including pre-filled edit workflows.

Compare 6 skills from other repositories ↓
View source ↗ Cratis/AI
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/Cratis/AI
agentmods
npx agentmods add skills/cratis/ai/cratis-components-stepper-command-dialog

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for cratis-components-stepper-command-dialog

README.md
[![agentmods](https://agentmods.dev/badge/skills/cratis/ai/cratis-components-stepper-command-dialog.svg)](https://agentmods.dev/skills/cratis/ai/cratis-components-stepper-command-dialog)
Your own site
<a href="https://agentmods.dev/skills/cratis/ai/cratis-components-stepper-command-dialog"><img src="https://agentmods.dev/badge/skills/cratis/ai/cratis-components-stepper-command-dialog.svg" alt="Measured on agentmods" height="20"></a>
Per session 95 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,067 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00095 $0.02067
Opus 5 $0.00048 $0.01033
Sonnet 5 $0.00019 $0.00413
Haiku 4.5 $0.00010 $0.00207

Measured yesterday against content hash f81909a95d12, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

cratis-components-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 yesterday.

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.

skills/cratis-components-stepper-command-dialog/SKILL.md · 210 lines

How it starts

The opening of the file, as written. The whole thing — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Cratis Components stepper command dialogs

StepperCommandDialog splits one command's form across named steps. The user moves with Previous and Next; Submit appears on the last step once every field across every step is valid.

Verified product sources

Package Version Verified from
@cratis/components 3.0.0 its package manifest and CommandDialog sources
@cratis/arc.react >=20.3.1 <23 peer range declared by @cratis/[email protected]
primereact ^11.0.0 peer of @cratis/[email protected]

Choose it over CommandDialog when

  • the form has too many fields to show at once;
  • the fields group into logical stages ("Contact → Details → Budget");
  • guided linear input with per-step feedback is what the task deserves.

A four-field form is usually still an ordinary CommandDialog.

Step 1 — One command for the whole wizard

Every step contributes properties to the same command instance. Define the command on the backend and run a Debug build so the TypeScript proxy exists before importing it.

Step 2 — Build the dialog

import { StepperCommandDialog, StepperPanel } from '@cratis/components/CommandDialog';
import { InputTextField, NumberField, TextAreaField } from '@cratis/components/CommandForm';
import { DialogResult, useDialogContext } from '@cratis/arc.react/dialogs';
import { CreateProject } from '../api/Projects/CreateProject';

export const CreateProjectDialog = () => {
    const { closeDialog } = useDialogContext();

    return (
        <StepperCommandDialog<CreateProject>
            command={CreateProject}
            title='Create new project'
            okLabel='Create'
            onSuccess={() => closeDialog(DialogResult.Ok)}
            onCancel={() => closeDialog(DialogResult.Cancelled)}>
            <StepperPanel header='Contact info'>
                <InputTextField<CreateProject> value={c => c.email} title='Contact email' type='email' />
            </StepperPanel>
            <StepperPanel header='Project details'>
                <InputTextField<CreateProject> value={c => c.name} title='Project name' />
                <TextAreaField<CreateProject> value={c => c.description} title='Description' rows={4} />
            </StepperPanel>
            <StepperPanel header='Budget'>
                <NumberField<CreateProject> value={c => c.budget} title='Budget' />
            </StepperPanel>
        </StepperCommandDialog>
    );
};

Read the full file on GitHub · 210 lines

Files

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.

Changes

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.

  1. yesterday First seen · 210 lines · 95 tokens per session scan A f81909a95d12

Subscribe to this mod's changes

cratis-components-stepper-command-dialog is a skill published in the GitHub repository Cratis/AI (2 stars, last pushed yesterday), licensed MIT. It adds 95 tokens to every session and 2,067 once invoked, about $0.0005 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-09-06.

Related

Other skills, from other repositories

sharpconsoleui

Use SharpConsoleUI to build full terminal (TUI) applications in .NET — equally suited to full-screen single-window apps and multi-window desktops with overlapping draggable windows — using a compositor, a DOM layout engine, and 40+ reactive controls (data tables, tree views, forms, an embedded PTY terminal, markdown…

managedcode/dotnet-skills · 190 tokens

mvvm

Implement the Model-View-ViewModel pattern in .NET applications with proper separation of concerns, data binding, commands, and testable ViewModels using MVVM Toolkit. USE FOR: implementing UI separation with Model-View-ViewModel; using MVVM Toolkit (CommunityToolkit.Mvvm) for ViewModels; designing testable UI…

managedcode/dotnet-skills · 120 tokens

astro-developer

Comprehensive guide for developing in the Astro monorepo. Covers architecture, debugging, testing, and critical constraints. Use when working on features, fixes, tests, or understanding the codebase structure.

managedcode/dotnet-skills · 44 tokens

sonarjs

Use SonarJS-derived rules in .NET repositories that ship JavaScript or TypeScript frontends and need deeper bug-risk, code-smell, or cognitive-complexity checks than a minimal ESLint baseline. USE FOR: SonarQube, SonarCloud, or eslint-plugin-sonarjs setups; frontend code smells; cognitive complexity and deeper…

managedcode/dotnet-skills · 132 tokens

biome

Use Biome in .NET repositories that ship Node-based frontend assets and want a fast combined formatter-linter-import organizer for JavaScript, TypeScript, CSS, JSON, GraphQL, or HTML. USE FOR: biome.json or @biomejs/biome setup; fast frontend formatting and linting; replacing overlapping frontend style tools…

managedcode/dotnet-skills · 126 tokens

eslint

Use ESLint in .NET repositories that ship JavaScript, TypeScript, React, or other Node-based frontend assets. USE FOR: the repo has package.json, eslint.config., .eslintrc, tsconfig.json, or JS/TS/React frontend files; the user asks for JavaScript or TypeScript linting, React rule. DO NOT USE FOR: CSS ownership by…

managedcode/dotnet-skills · 131 tokens