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 skills add aiocean/claude-plugins --skill aio-xstategit clone --depth 1 https://github.com/aiocean/claude-pluginsWrote 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/aiocean/claude-plugins/aio-xstate)<a href="https://agentmods.dev/skills/aiocean/claude-plugins/aio-xstate"><img src="https://agentmods.dev/badge/skills/aiocean/claude-plugins/aio-xstate.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.00103 | $0.01301 |
| Opus 5 | $0.00051 | $0.00651 |
| Sonnet 5 | $0.00021 | $0.00260 |
| Haiku 4.5 | $0.00010 | $0.00130 |
Grade A, and why
aio-xstate 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 3d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
XState v5 Strict Skill
Environment
- tsc: !
tsc --version 2>/dev/null || echo "NOT INSTALLED"
XState v5 ONLY. Requires TypeScript 5.0+. Never use v4 patterns.
Workflow
- Design first (unless user says skip): produce planning artifacts before code
- Types first:
types.context,types.events,types.input(+types.output) - Implement:
setup({...}).createMachine({...})with all implementations in setup - Validate:
tsc --noEmit, noanyleaks, no string events, no v4 imports
Quick Reference
import { setup, assign, fromPromise, createActor } from "xstate"
const machine = setup({
types: {
context: {} as { count: number },
events: {} as { type: "inc" } | { type: "add"; amount: number },
input: {} as { initialCount?: number },
},
actions: {
inc: assign({ count: ({ context }) => context.count + 1 }),
add: assign({
count: ({ context }, params: { amount: number }) => context.count + params.amount,
}),
},
guards: {
isPositive: ({ context }) => context.count > 0,
},
}).createMachine({
id: "counter",
context: ({ input }) => ({ count: input.initialCount ?? 0 }),
initial: "active",
states: {
active: {
on: {
inc: { actions: "inc" },
add: {
actions: {
type: "add",
params: ({ event }) => ({ amount: event.amount }),
},
},
},
},
},
})
const actor = createActor(machine, { input: { initialCount: 0 } })
actor.subscribe((snapshot) => console.log(snapshot.context.count))
actor.start()
actor.send({ type: "inc" })
Hard Rules
setup({...}).createMachine({...})for all machines- All implementations in
setup(): actions, guards, actors - Typed params: actions/guards take
(_, params: { ... })second arg - Event objects only:
actor.send({ type: "X" }), never strings - No god-machine: unrelated domains = separate actors/machines
- No state-mirroring booleans: use state nodes for modes, context for data
invokehasonError: always handle failure- No v4 patterns: no
interpret,Machine,cond,send,pure,choose
What ships with it
2 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.
- 3d ago First seen · 128 lines · 103 tokens per session scan A 746f57d49460
aio-xstate is a skill published in the GitHub repository aiocean/claude-plugins (4 stars, last pushed 4d ago), licensed MIT. It adds 103 tokens to every session and 1,301 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
frontend-component
Create React/Vue component with TypeScript, tests, and styles. Auto-invoke when user says "create component", "add component", "new component", or "build component".
coding-standards
A set of general coding standards and practical patterns for TypeScript, JavaScript, React, and Node.js. It covers readable naming, simple designs, avoiding repetition, and delaying unnecessary features.
react-component-generator
Generate React components with TypeScript, proper props, hooks, and accessibility. Use when creating new React components, UI elements, or refactoring existing components.
react-dev
Explicit /react-dev reference for advanced React/TypeScript typing and integration patterns. Do not auto-use for routine React implementation.
react-modernization
Upgrade React applications to latest versions, migrate from class components to hooks, and adopt concurrent features. Use when modernizing React codebases, migrating to React Hooks, or upgrading to latest React versions.
senior-frontend
Frontend development skill for React, Next.js, TypeScript, and Tailwind CSS applications. Use when building React components, optimizing Next.js performance, analyzing bundle sizes, scaffolding frontend projects, implementing accessibility, or reviewing frontend code quality.