Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/cratis/verticalslices/scaffold-featurenpx skills add Cratis/VerticalSlices --skill scaffold-featuregit 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/scaffold-feature)<a href="https://agentmods.dev/skills/cratis/verticalslices/scaffold-feature"><img src="https://agentmods.dev/badge/skills/cratis/verticalslices/scaffold-feature.svg" alt="Measured on agentmods" 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.00050 | $0.00535 |
| Opus 5 | $0.00025 | $0.00267 |
| Sonnet 5 | $0.00010 | $0.00107 |
| Haiku 4.5 | $0.00005 | $0.00053 |
Grade A, and why
scaffold-feature 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 5d 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 scaffold-feature — 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.
What it actually says
Scaffold a brand-new feature folder with routing and navigation — ready for slices.
What to produce
1 — Feature folder
<Feature>/ ← directly under the app source root (or under an optional <Module>/) — no Features/ wrapper
├── <Feature>.tsx ← composition page
├── <Feature>.css ← feature-level styles (can be empty initially)
└── index.ts ← re-exports the composition page
2 — Composition page (<Feature>.tsx)
// Copyright (c) Cratis. All rights reserved.
// Licensed under the MIT license. See LICENSE file in the project root for full license information.
import { Page } from '@cratis/components/Common';
export const <Feature> = () => {
return (
<Page title="<NavigationLabel>">
{/* Slices will be composed here */}
</Page>
);
};
3 — index.ts
// Copyright (c) Cratis. All rights reserved.
// Licensed under the MIT license. See LICENSE file in the project root for full license information.
export { <Feature> } from './<Feature>';
4 — Update routing
Locate the app router (typically App.tsx or a routes.ts file) and add:
import { <Feature> } from './<Feature>';
{ path: '<route-path>', element: <<Feature> /> }
5 — Update navigation
Locate the sidebar/navigation configuration and add:
import * as mdIcons from 'react-icons/md';
{
label: '<NavigationLabel>',
icon: mdIcons.<NavigationIcon>,
url: '<route-path>'
}
Rules
- Feature name: PascalCase (e.g.
Projects,Invoices) - Route path: kebab-case (e.g.
/projects,/user-management) - Navigation icon: from
react-icons/md— e.g.MdFolderOpen,MdPeople - Copyright header on every file
Validation
Run yarn lint and npx tsc -b. Fix all errors. Confirm the blank page renders without runtime errors.
Next step
Add slices using the new-vertical-slice skill.
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.
- 5d ago First seen · 83 lines · 50 tokens per session scan A 1475435927c0
scaffold-feature is a skill published in the GitHub repository Cratis/VerticalSlices (2 stars, last pushed 2d ago), licensed MIT. It adds 50 tokens to every session and 535 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to scaffold-feature, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
cratis-react-page
Step-by-step guidance for building a React page in a Cratis Arc application — DataPage lists, CommandDialog toolbar actions, confirmation and busy-indicator dialogs, row selection, details components, observable queries, and MVVM. Use when building or modifying a page that lists/displays data, adding a table, wiring…
toolbar
Use this skill when asked to add or build a canvas-style icon toolbar using the @cratis/components Toolbar component. Covers Toolbar, ToolbarButton, ToolbarSeparator, ToolbarSection, ToolbarContext, and ToolbarFanOutItem. Use whenever building tool panels, drawing tool selectors, zoom controls, or any icon-button…
add-traces
Use this skill when asked to add OpenTelemetry tracing to a class in a Cratis Chronicle Kernel project. Produces Traces.cs companion files using the [Span] source-generator pattern from Cratis.Traces, registers IActivitySource as a keyed DI service, and injects it into the target class.
auth-and-identity
Use this skill for authentication, authorization, or identity in a Cratis Arc project — backend, frontend, or both. Covers identity providers (IProvideIdentityDetails), protecting commands/queries with authorization attributes, Microsoft Identity Platform, connecting backend identity to React, multi-tenant identity…
cratis-specs-csharp
Step-by-step guidance for writing C# specs in Cratis with BDD Specification by Example — the Establish/Because/should pattern, for/when/and folder hierarchy, reusable given/ contexts, NSubstitute mocking, and the in-process scenario family. Use when writing C# unit or integration specs or structuring the for/when/and…
cratis-fundamentals-concept
Create strongly typed Cratis domain values with ConceptAs and Chronicle event-source identities with EventSourceId . Use when a C# domain value has meaning beyond its primitive or when an identity is actually used as a Chronicle event-source/stream ID. Do not use for enums, DTO-only transport values, arbitrary…