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/toolbar/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/toolbar)<a href="https://agentmods.dev/skills/cratis/verticalslices/toolbar"><img src="https://agentmods.dev/badge/skills/cratis/verticalslices/toolbar/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/toolbar"><img src="https://agentmods.dev/badge/skills/cratis/verticalslices/toolbar.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.00078 | $0.02389 |
| Opus 5.5 | $0.00031 | $0.00956 |
| Sonnet 5.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 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 toolbar — 14 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 — 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.
- 1mo ago First seen · 283 lines · 78 tokens per session scan A 151cfeecaa91
toolbar is a skill published in the GitHub repository Cratis/VerticalSlices (2 stars, last pushed 1mo ago), licensed MIT. It adds 78 tokens to every session and 2,389 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 toolbar, differing in 14 lines, and is treated as a copy.
Other skills, from other repositories
cratis-components-common-controls
Choose and bind Cratis Components ComboBox, ToggleGroup, Tabs, TagGroup and Breadcrumbs with controlled values, query states, keyboard semantics and localizable names. Use for entity pickers, exclusive choices, panel tabs, tag inputs or navigation trails. Do not use for Arc generated command fields, data tables…
cratis-primereact-ui-basics
Baseline UI/UX standards for building React frontends on Cratis Components (PrimeReact theming/tokens) - usable, accessible, consistent screens. Use when building or modifying a Cratis Arc React page, form, dialog, or list; when adding a PrimeReact-backed control; or when reviewing a Cratis frontend change for sizing…
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-react-page
Build a React page in a Cratis Arc application with Cratis Components — DataPage lists, columns, toolbar menu items, command dialogs, confirmation and busy-indicator dialogs, row selection, details panes, snapshot and observable queries, paging, and MVVM view models. Use when building or changing a page that lists or…
cratis-components-styling
Style and theme an application built on Cratis Components 4 — the three stylesheet entries an app must import, the --cratis- design-token seam, choosing between the baseline theme, a product theme and fully owned styling, dark mode, the typed pt parts and data-cratis-part selectors, the optional renderer adapters, and…
cratis-components-data-surfaces
Compose Cratis Components PivotViewer exploration, TimeMachine historical snapshots, Canvas pan/zoom boards and public Chat conversation/sidebar surfaces. Use when a table is not the right presentation, when supplying Pixi-backed content, or when binding host-owned chat data and actions. Do not use for DataPage lists…