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.
git 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/rules/chakra-ui/ark/svelte)<a href="https://agentmods.dev/rules/chakra-ui/ark/svelte"><img src="https://agentmods.dev/badge/rules/chakra-ui/ark/svelte/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/rules/chakra-ui/ark/svelte"><img src="https://agentmods.dev/badge/rules/chakra-ui/ark/svelte.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.00255 | $0.00255 |
| Opus 5.5 | $0.00102 | $0.00102 |
| Sonnet 5.5 | $0.00051 | $0.00051 |
| Haiku 4.5 | $0.00026 | $0.00026 |
Grade A, and why
svelte 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.
What it actually says
- Make sure to export the
*BaseProps children?: Snippetalready exists inHTMLArkProps<X>so no need to define it- Every
use*hook must return andAccessor<T> - For
*-root.sveltefiles wherevalueoropenis a valid prop, make sure you setup the$bindable()for it. - For
*-context.sveltefiles, prefer to userendernotchildrenprop
Exporting Files
- Always export pattern is
export { default as Component } - Check the exports against the react package and make sure they're the same
Creating Stories
- When creating stories, keep the format simple
- Imports must have a
Examplesuffix - All imports in examples must use
@ark-ui/svelte/<component>
import BasicExample from "./examples/basic.svelte"
const meta: Meta = {
title: 'Components / <component>',
}
export default meta
export const Basic = {
render: () => ({
Component: BasicExample,
}),
}
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 · 39 lines · 255 tokens per session scan A c2ed3f5a8282
svelte is a cursor rule published in the GitHub repository chakra-ui/ark (5,421 stars, last pushed today), licensed MIT. It adds 255 tokens to every session, about $0.0010 per session on Opus 5.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 cursor rules, from other repositories
cursorrules
You are using StyleSeed, a design-method engine whose goal is to make expert design judgment repeatable by coding agents, not to replace designers with aesthetic preferences. Preserve approved project choices; report unsupported choices instead of silently restyling the project's design system. PRODUCT-PRINCIPLES.md…
general
Wonder Blocks design system conventions, component patterns, and coding standards.
mdc-files
Best practices for writing .mdc cursor rules files.
app-router
Next.js App Router patterns, React component standards, and project structure.
frontend
React/Next.js frontend coding standards with shadcn/ui, Tailwind CSS v4, and FSD-lite architecture.
material-icons
use material icons for icons.