Compozy is a system for coordinating AI coding agents, allowing command-line agents to divide work, exchange tasks, run scheduled or repeated jobs, and share project memory under browser supervision. Developers and technical operators use it to create, automate, and monitor ongoing agent work. The catalogue entries provide skills and other add-ons for its agent workflows.
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/compozy/compozy/xstate-storenpx skills add compozy/compozy --skill xstate-storegit clone --depth 1 https://github.com/compozy/compozyWrote 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/compozy/compozy/xstate-store)<a href="https://agentmods.dev/skills/compozy/compozy/xstate-store"><img src="https://agentmods.dev/badge/skills/compozy/compozy/xstate-store.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 | $0.00123 | $0.00881 |
| Opus 5 | $0.00062 | $0.00441 |
| Sonnet 5 | $0.00025 | $0.00176 |
| Haiku 4.5 | $0.00012 | $0.00088 |
Grade A, and why
xstate-store 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.
How it starts
The opening of the file, as written. The whole thing — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
XState Store
Targets @xstate/store v4 and @xstate/store-react v2 (TypeScript 5.4+). Match the task to one or more Branches rows and read every listed file in full before producing output — those references are the contract; the tripwires below are only a final self-check.
Pick the primitive first
| State | Primitive | Why |
|---|---|---|
| Domain state updated through named events | createStore({ context, on }) |
Typed trigger, can, emitted events, replayable transitions |
| Per-instance state built from input | createStoreLogic({ context: (input) => … }) |
One definition, many instances; selectors come along |
| A single value set directly | createAtom(value) |
No event vocabulary to justify a store |
| A value computed from other atoms or selectors | createAtom(() => …) |
Read-only, recomputes on dependency change |
| Modes, guards, delays, hierarchical or parallel states | xstate machine |
A store models data, not lifecycle |
Done when: the primitive is chosen from this table and its justification holds.
Branches
| When you are… | Read in full |
|---|---|
Creating a store, writing transitions, using trigger/send/can, or Immer |
references/store-core.md |
| Enqueuing effects, emitting events, or doing async work | references/effects-and-events.md |
Declaring schemas or turning on runtime validation |
references/schemas-and-validation.md |
Reading state with store.select, atoms, derived/async/reducer atoms |
references/selectors-and-atoms.md |
Building reusable/per-instance stores with createStoreLogic, input, or selectors |
references/store-logic-and-input.md |
Adding persist, undoRedo, reset, or composing .with(...) |
references/extensions.md |
| Wiring a store into React components | references/react.md |
| Testing transitions, inspecting a store, or interoperating with XState | references/testing-and-interop.md |
| Upgrading a v3 store to v4, or porting an existing Zustand store over | references/migration-v4.md |
What ships with it
9 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.
- references/effects-and-events.md 3.5 KB
- references/extensions.md 7.7 KB
- references/migration-v4.md 5.4 KB
- references/react.md 5.9 KB
- references/schemas-and-validation.md 4.1 KB
- references/selectors-and-atoms.md 4.8 KB
- references/store-core.md 3.8 KB
- references/store-logic-and-input.md 3.0 KB
- references/testing-and-interop.md 4.0 KB
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 · 51 lines · 123 tokens per session scan A 84a834cd7e7e
xstate-store is a skill published in the GitHub repository compozy/compozy (2,713 stars, last pushed 2d ago), licensed MIT. It adds 123 tokens to every session and 881 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-09-03.
Other skills, from other repositories
frontend-conventions
Coding conventions, architecture patterns, and testing rules for the SkillHub React frontend. Ensures agents follow Feature-Sliced Design and use the generated OpenAPI types.
frontend-dev-guidelines
Frontend development guidelines for React/TypeScript applications. Modern patterns including Suspense, lazy loading, useSuspenseQuery, file organization with features directory, MUI v7 styling, TanStack Router, performance optimization, and TypeScript best practices. Use when creating components, pages, features…
fast-typescript-check
Keep www-sacred's TypeScript fast to type-check and fast to run. Use when touching the ASCII/canvas animation components (the only real per-frame code here), tightening type-check wall-clock, or auditing a change for runtime or compiler regressions. Scoped to this repo — a React 19 / Next.js 16 component library plus…
typescript-react
Apply, review, and explain React conventions from the TypeScript Style Guide. Use automatically for TypeScript and TSX tasks involving prop-derived state, prop typing, component responsibilities, data flow, compound components, or client and server state.
electron-dev
Electron desktop apps with React, TypeScript, and Vite. Use for IPC, window/tray, PTY terminals, WebRTC, and packaging.
coding-standards
TypeScript、JavaScript、React、Node.js開発のための汎用コーディング標準、ベストプラクティス、パターン。.