Ark UI is a headless component library: it supplies accessible UI behavior and structure without visual styling, so developers can build their own design systems. It supports React, Vue, Solid, and Svelte applications.
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 commands/chakra-ui/ark/zag-changeloggit clone --depth 1 https://github.com/chakra-ui/arkWrote 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/commands/chakra-ui/ark/zag-changelog)<a href="https://agentmods.dev/commands/chakra-ui/ark/zag-changelog"><img src="https://agentmods.dev/badge/commands/chakra-ui/ark/zag-changelog.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.00018 | $0.00962 |
| Opus 5 | $0.00009 | $0.00481 |
| Sonnet 5 | $0.00004 | $0.00192 |
| Haiku 4.5 | $0.00002 | $0.00096 |
Grade A, and why
zag-changelog 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 5d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Steps
-
Fetch the latest CHANGELOG.md from the chakra-ui/zag repository
- Use
gh api repos/chakra-ui/zag/contents/CHANGELOG.md -H "Accept: application/vnd.github.raw+json"to get the changelog content
- Use
-
Determine which Zag versions are new
- Check the current
@zag-js/*version inpackages/react/package.json - Compare the latest Ark UI release changelog (
packages/react/CHANGELOG.md) against the Zag changelog - Identify Zag versions whose changes are NOT yet reflected in the Ark UI changelogs
- Check the current
-
Parse the new changes from Zag.js changelog
- Extract all entries from the new Zag versions
- Identify component-specific changes and general improvements
- Filter out Zag.js internal changes that don't affect Ark UI (build system, core state machine internals, docs-only, framework-specific fixes for frameworks Ark doesn't use like Preact/Vanilla)
-
Review the changes with me before applying
- Show me the extracted changes
- Confirm which changes should be synced to Ark UI
- Ask if any changes need framework-specific notes
-
Create a changeset file in
.changeset/- Use the format from existing changesets (YAML frontmatter with package names and bump type)
- Include all four frameworks:
@ark-ui/react,@ark-ui/solid,@ark-ui/svelte,@ark-ui/vue - Use
patchfor bug fixes,minorfor new features - Do NOT modify the
CHANGELOG.mdfiles directly
-
Show me a summary of all changes made
- List which components were updated
- Highlight any differences between frameworks (if applicable)
Important Notes
- Only sync changes that are relevant to Ark UI components
- Skip Zag.js internal changes (build system, documentation-only, core machine internals, etc.)
- Create changesets (
.changeset/*.md) instead of editing CHANGELOG.md files directly
Writing Style
Follow the tone guide in TONE_OF_VOICE.md. Changelogs are user-facing — write them like you're telling a developer
what's new, not filing a spec.
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.
- 5d ago First seen · 101 lines · 18 tokens per session scan A da32923978c0
zag-changelog is a command published in the GitHub repository chakra-ui/ark (5,373 stars, last pushed yesterday), licensed MIT. It adds 18 tokens to every session and 962 once invoked, about $0.0001 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-30.
Other commands, from other repositories
new-primitive
Scaffold a new headless Angular primitive in packages/primitives/ /, following current project conventions (signals-first, no CDK, newer suffix-less naming).
dev-react-headless
Command "dev-react-headless" from daangn/seed-design, covering react headless 개발, 인자 and 필수 결과.
write-react-component-docs
Command "write-react-component-docs" from daangn/seed-design, covering react 컴포넌트 문서 작성, 인자 and 필수 결과.
component
Create new React component.
gen-video
Generate video output in one of three modes: Remotion (programmatic React-based video), Gen-AI (shot prompt pack for Runway/Kling/Sora/Pika/Luma), or Remotion+Gen-AI (programmatic scaffold with AI footage embedded).
override
Override an @marmoui/ui component or create a new custom component in the app's local ui/ folder — sets up the wrapper convention (src/ui/ re-exporting @marmoui/ui) on first run, then shadows or adds components without forking the package.