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/open-circle/agent-skills/formischnpx skills add open-circle/agent-skills --skill formischgit clone --depth 1 https://github.com/open-circle/agent-skillsWrote 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/open-circle/agent-skills/formisch)<a href="https://agentmods.dev/skills/open-circle/agent-skills/formisch"><img src="https://agentmods.dev/badge/skills/open-circle/agent-skills/formisch.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.00064 | $0.07817 |
| Opus 5 | $0.00032 | $0.03908 |
| Sonnet 5 | $0.00013 | $0.01563 |
| Haiku 4.5 | $0.00006 | $0.00782 |
Grade A, and why
formisch 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 — 1,119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Formisch
This skill helps AI agents work effectively with Formisch, the schema-based, headless form library for modern frameworks.
When to Use This Skill
- When the user asks about form handling with Formisch
- When managing form state and validation
- When working with Angular, Preact, Qwik, React, React Native, Solid, Svelte, or Vue forms
- When integrating Valibot schemas with forms
Introduction
Formisch is a schema-based, headless form library that works across multiple frameworks. Key highlights:
- Small bundle size — Starting at ~2.5 kB
- Schema-based validation — Uses Valibot for type-safe validation
- Headless design — You control the UI completely
- Type safety — Full TypeScript support with autocompletion
- Framework-native — Native performance for each supported framework
Supported Frameworks
| Framework | Package | Hook/Primitive |
|---|---|---|
| Angular | @formisch/angular |
injectForm |
| Preact | @formisch/preact |
useForm |
| Qwik | @formisch/qwik |
useForm$ |
| React | @formisch/react |
useForm |
| React Native | @formisch/react-native |
useForm |
| SolidJS | @formisch/solid |
createForm |
| Svelte | @formisch/svelte |
createForm |
| Vue | @formisch/vue |
useForm |
Installation
1. Install Valibot (peer dependency)
npm install valibot
2. Install Formisch for your framework
npm install @formisch/react # React
npm install @formisch/angular # Angular
npm install @formisch/vue # Vue
npm install @formisch/solid # SolidJS
npm install @formisch/preact # Preact
npm install @formisch/svelte # Svelte
npm install @formisch/qwik # Qwik
npm install @formisch/react-native # React Native
What ships with it
1 file 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.
- 5d ago First seen · 1,119 lines · 64 tokens per session scan A 20d7ec7777e3
formisch is a skill published in the GitHub repository open-circle/agent-skills (15 stars, last pushed 14d ago), licensed MIT. It adds 64 tokens to every session and 7,817 once invoked, about $0.0003 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…