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/dravensoft-dev/arena/designnpx skills add dravensoft-dev/arena --skill designgit clone --depth 1 https://github.com/dravensoft-dev/arenaWhat 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.00110 | $0.04018 |
| Opus 5 | $0.00055 | $0.02009 |
| Sonnet 5 | $0.00022 | $0.00804 |
| Haiku 4.5 | $0.00011 | $0.00402 |
Grade A, and why
design 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.
How it starts
The opening of the file, as written. The whole thing — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Arena
Arena is Dravensoft's design language: a token layer, React and Angular component libraries built on it, and a shared Tailwind layer. Its identity is warm black under bone text, crimson as the voice and gold as distinction.
Arena is a product-application library: tables, forms, navigation, dialogs, charts, cards and
the states around them, the furniture of an application somebody works in. A media or a consumer
product is a different register, so a photo wall, a feed of posts, a document editor or a game
map is markup you write yourself; the skin travels either way, because a style plugin answers
every role whatever the product is. When that is your product, or one screen of it,
references/media-register.md is what Arena hands you instead
of a component: the pattern your markup binds, the parts the package already ships for it, and
the one rule that bends.
This file routes. Read only what your task needs. The rules below bind the code you write; the table under them routes. Read the rules once rather than per screen.
Which job is this?
Building something with Arena (a screen, a prototype, a skin, an integration): stay here, and
follow the table below. On a project you have not walked yet, start at
references/cold-start.md instead, whose first question is whether
the project already carries Arena: one that does is a short walk that reads the config and the
plugin it already has, and one that does not is the only page asking what this product looks like
before anything answers.
Changing Arena itself (adding a component, moving a token, editing a contract or a gate):
read AGENTS.md instead. It is the
root of that branch and this file is not, and it is named by URL because that branch is the
repository's and reaches nothing a package or this site carries.
A value you answer is not a value you move, which is what decides the branch when the job is
an appearance: a role your project fills is this branch's whatever it paints, and a scale step
every product reads is the other one's, the type and page rhythm ladders aside. Every path here outside references/ is a repository
path, carried by a clone, by the plugin, and by the copy arena-to-prod --skill
installs; read on the repository above otherwise.
What ships with it
7 files 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.
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 · 200 lines · 110 tokens per session scan A 245b9da3f6bb
design is a skill published in the GitHub repository dravensoft-dev/arena (2 stars, last pushed 9d ago), licensed MIT. It adds 110 tokens to every session and 4,018 once invoked, about $0.0006 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
spartan
Manages spartan/ui, the Angular UI library - adding, composing, fixing, debugging, and styling UI with the Brain (headless primitives) and Helm (styled) layers. Provides project context, component APIs, and usage examples. Applies when working with spartan/ui, @spartan-ng/brain, @spartan-ng/helm, the @spartan-ng/cli…
ng-blatui
Use the ng-blatui Angular UI library in an app — install, import components (bui-prefixed, signal-based, zoneless, SSR-safe), theme with Tailwind v4 + oklch tokens, localize dates/numbers/labels, and discover the full catalog via the registry, api.json, llms.txt or the ng-blatui-mcp MCP server. Invoke when building…
neuralng-angular
Build or update Angular 22+ interfaces with NeuralNg when exact component selection, imports, forms, accessibility, SSR, icons, or theming guidance is needed.
angular-best-practices
Official Angular v22 coding best practices — signals, standalone, native control flow, zoneless, host bindings, Signal Forms, inject(), and accessibility (WCAG AA / AXE). Use whenever writing, generating, or reviewing Angular/TypeScript code in this repo.
create-db-component
Creates a new DB UX Design System component with Mitosis source, SCSS, typed model, and Playwright tests.
modify-db-component
Modifies an existing DB UX Design System Mitosis component (add variants, update props, change styles).