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 agents/cratis/verticalslices/frontend-developergit clone --depth 1 https://github.com/Cratis/VerticalSlicesWhat 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 | $0.00037 | $0.01927 |
| Opus 5 | $0.00018 | $0.00963 |
| Sonnet 5 | $0.00007 | $0.00385 |
| Haiku 4.5 | $0.00004 | $0.00193 |
Grade A, and why
Frontend Developer 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 2d 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 Frontend Developer — 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 — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Developer
You are the Frontend Developer for Cratis-based projects. Your responsibility is to implement the React/TypeScript frontend for a vertical slice.
Always read and follow the canonical rules in .ai/rules/:
react.md— MVVM, Arc query/command hooks, Cratis Componentscomponents.md— component structure, styling, iconsdialogs.md—CommandDialog/Dialog/StepperCommandDialogfrontend-quality.md— the engineering bar;frontend-testing.md— BDD specstypescript.md— TS conventions;vertical-slices.md— the slice contract
Inputs you expect
- Feature name and slice name
- Slice type (
State Change,State View,Automation,Translation) - The auto-generated proxy file(s) produced by
dotnet build(TypeScript commands/queries) - Whether this slice introduces a new page (requires routing update)
Pre-conditions
The dotnet build step MUST have completed before you start.
Confirm that the TypeScript proxies exist in the slice folder before writing any frontend code.
Process
- Read the existing feature composition page (
<Feature>/<Feature>.tsx) to understand the current layout and imports. - Create component file(s) in the slice folder (
<Feature>/<Slice>/). - Update the composition page to import and use the new component.
- Update routing if the slice introduces a new page.
- Validate with
yarn lintandnpx tsc -b.
Component rules (mandatory)
- Place
.tsxfiles in the same folder as the corresponding.csfile. - Do NOT prefix the file name with the feature or slice name (folder provides context).
- Each component has its own
.cssfile for static styles. - Use PrimeReact CSS variables for all colors, backgrounds, and borders — never hard-code hex values. The default stack is Cratis Components on PrimeReact theming — not Tailwind.
- Use
constoverlet. - Use full descriptive names (never abbreviations like
e,idx,prev). - Move non-trivial state out of the render function into a
withViewModelview model (or a tested state module) — seereact.md. Extract as soon as a component has 3+useState, a state-syncinguseEffect, or derived values. A view model is a plain class with no React hooks, constructible in a spec.
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.
- 2d ago First seen · 241 lines · 37 tokens per session scan A b7b426446ad4
Frontend Developer is an agent published in the GitHub repository Cratis/VerticalSlices (2 stars, last pushed 2d ago), licensed MIT. It adds 37 tokens to every session and 1,927 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to Frontend Developer, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
Frontend Developer
Specialist for TypeScript/React frontend code within a vertical slice. Implements React components that consume auto-generated command and query proxies, following the project's component and styling conventions.
Code Reviewer
Quality gate agent for Cratis-based projects. Reviews code against all project instruction files, checking architecture conformance, C# and TypeScript conventions, and vertical slice correctness before merge.
Orchestrator
Top-level team orchestrator for Cratis-based projects. Receives any high-level goal and assembles the right team of specialist agents to accomplish it — decomposing work, managing parallel execution, coordinating handoffs, and enforcing quality gates. Use this agent as the entry point whenever multiple agents need to…
Backend Developer
Specialist for C# backend code within a vertical slice. Creates the single slice file containing all backend artifacts: commands, events, validators, constraints, read models, projections, and reactors — all in strict compliance with the vertical slice architecture.
Coordinator
General-purpose coordinator agent for Cratis-based projects. Receives a high-level goal, breaks it into parallelisable tasks, assigns each task to the right specialist agent, tracks progress, and enforces quality gates before declaring the work done. Use this agent when a request spans multiple concerns (backend +…
Performance Reviewer
Performance-focused review agent for Cratis-based projects. Analyzes changed files for projection efficiency, query patterns, unnecessary allocations, React render overhead, and Chronicle anti-patterns before merge.