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/ai/toolbarnpx skills add Cratis/AI --skill toolbargit clone --depth 1 https://github.com/Cratis/AIWhat 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.00078 | $0.02389 |
| Opus 5 | $0.00039 | $0.01195 |
| Sonnet 5 | $0.00016 | $0.00478 |
| Haiku 4.5 | $0.00008 | $0.00239 |
Grade A, and why
toolbar 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- toolbar — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 283 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to use the Toolbar
The Toolbar component is designed for canvas-style tool panels — the kind you find in drawing or diagram editors. It groups ToolbarButton elements into a pill-shaped bar with hover tooltips and active highlights. Use it when you need:
- A tool selector with an "active tool" state
- A set of action buttons that animate between tool modes
- A toolbar that fans out sub-panels for grouped tools
For a standard page action menu (Create / Edit / Delete over a data table), use DataPage.MenuItems instead.
Component overview
| Component | Purpose |
|---|---|
Toolbar |
Container — renders a pill-shaped bar of buttons |
ToolbarButton |
Icon or text button with tooltip and optional active state |
ToolbarSeparator |
Visual divider between button groups |
ToolbarSection |
Animated section that transitions between named contexts |
ToolbarContext |
Named set of buttons inside a ToolbarSection |
ToolbarFanOutItem |
Button that slides out a horizontal sub-panel on click |
All components import from the @cratis/components/Toolbar subpath (never the root barrel — see components.md):
import { Toolbar, ToolbarButton, ToolbarSeparator, ToolbarSection, ToolbarContext, ToolbarFanOutItem } from '@cratis/components/Toolbar';
Step 1 — Basic vertical toolbar
Place ToolbarButton elements inside Toolbar. The default orientation is vertical.
import { Toolbar, ToolbarButton } from '@cratis/components/Toolbar';
export const DrawingToolbar = () => (
<Toolbar>
<ToolbarButton icon='pi pi-arrow-up-left' tooltip='Select' />
<ToolbarButton icon='pi pi-pencil' tooltip='Draw' />
<ToolbarButton icon='pi pi-stop' tooltip='Rectangle' />
</Toolbar>
);
Step 2 — Active state (selected tool)
Use the active prop to highlight the currently selected tool. Drive it from state:
import { useState } from 'react';
import { Toolbar, ToolbarButton } from '@cratis/components/Toolbar';
export const DrawingToolbar = () => {
const [activeTool, setActiveTool] = useState('select');
return (
<Toolbar>
<ToolbarButton
icon='pi pi-arrow-up-left'
tooltip='Select'
active={activeTool === 'select'}
onClick={() => setActiveTool('select')}
/>
<ToolbarButton
icon='pi pi-pencil'
tooltip='Draw'
active={activeTool === 'draw'}
onClick={() => setActiveTool('draw')}
/>
<ToolbarButton
icon='pi pi-stop'
tooltip='Rectangle'
active={activeTool === 'rect'}
onClick={() => setActiveTool('rect')}
/>
</Toolbar>
);
};
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.
- yesterday First seen · 283 lines · 78 tokens per session scan A 151cfeecaa91
toolbar is a skill published in the GitHub repository Cratis/AI (2 stars, last pushed 4d ago), licensed MIT. It adds 78 tokens to every session and 2,389 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-31.
Other skills, from other repositories
ship-changes
Ship staged or unstaged local changes: create a branch, make logical commits, push to origin, open a PR with the correct description and label, merge it, close the issues it resolves, and delete the branch locally and on origin. Use whenever the user asks to commit, push, create a PR, ship, or land changes.
add-concept
Use this skill when asked to create a strongly-typed domain identifier or value (such as ProjectId, AuthorName, InvoiceNumber) in a Cratis-based project. Produces a ConceptAs record with the correct conversions and sentinel values.
skill-creator
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, update or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
cratis-command
Step-by-step guidance for creating a Cratis Arc command — [Command] record, Handle() method, CommandValidator, proxy generation, and React .use() hook with CommandDialog. Use when adding or creating a command, wiring up a form or button to the backend, working with IEventLog, CommandResult, CommandValidator…
cratis-readmodel
Step-by-step guidance for creating a Cratis Chronicle read model from scratch — defining events, choosing between projection and reducer, [ReadModel] record with static query methods, and the generated TypeScript proxy in React. Use when creating a read model, working with [EventType], [ReadModel], IProjectionFor…
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…