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 asmyshlyaev177/state-in-url --skill form-library-integrationgit clone --depth 1 https://github.com/asmyshlyaev177/state-in-urlWrote 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/asmyshlyaev177/state-in-url/form-library-integration)<a href="https://agentmods.dev/skills/asmyshlyaev177/state-in-url/form-library-integration"><img src="https://agentmods.dev/badge/skills/asmyshlyaev177/state-in-url/form-library-integration/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/skills/asmyshlyaev177/state-in-url/form-library-integration"><img src="https://agentmods.dev/badge/skills/asmyshlyaev177/state-in-url/form-library-integration.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.00094 | $0.01894 |
| Opus 5.5 | $0.00038 | $0.00758 |
| Sonnet 5.5 | $0.00019 | $0.00379 |
| Haiku 4.5 | $0.00009 | $0.00189 |
Grade A, and why
form-library-integration 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 23d 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 — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.
This skill builds on state-in-url/feature-state-hook. Read it first for the module-scoped default-state rule.
state-in-url — Form library integration (react-hook-form)
The canonical pattern: one module-scoped defaults object owns the form shape, both useUrlState and useForm consume it, RHF's subscribe() callback pushes form changes into setUrl. Hydration from URL happens through defaultValues: urlState.
Setup
// features/filters/filtersState.ts
import { z } from 'zod';
export const filtersSchema = z.object({
q: z.string(),
sort: z.enum(['name', 'date']),
tags: z.array(z.string()),
});
export type FiltersState = z.infer<typeof filtersSchema>;
export const FILTERS_STATE: FiltersState = {
q: '',
sort: 'name',
tags: [],
};
// features/filters/FiltersForm.tsx
'use client';
import React from 'react';
import { useForm } from 'react-hook-form';
import { zodResolver } from '@hookform/resolvers/zod';
import { useUrlState } from 'state-in-url/next';
import { FILTERS_STATE, filtersSchema, type FiltersState } from './filtersState';
// `searchParams` forwarded by the server page that renders this form
export function FiltersForm({ searchParams }: { searchParams?: object }) {
const { urlState, setUrl } = useUrlState(FILTERS_STATE, { searchParams });
const form = useForm<FiltersState>({
resolver: zodResolver(filtersSchema),
defaultValues: urlState, // hydrate from URL on mount
});
React.useEffect(() => {
const sub = form.subscribe({
formState: { values: true },
callback: ({ values }) => setUrl(values),
});
return () => sub();
}, [form, setUrl]);
return (
<form>
<input {...form.register('q')} />
<select {...form.register('sort')}>
<option value="name">Name</option>
<option value="date">Date</option>
</select>
</form>
);
}
Core Patterns
Hydrate useForm from urlState
defaultValues: urlState runs once on mount; the form is initialized with whatever the URL contained (or FILTERS_STATE defaults if URL is empty).
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.
- 23d ago First seen · 212 lines · 94 tokens per session scan A 8ac4bd75fcfb
form-library-integration is a skill published in the GitHub repository asmyshlyaev177/state-in-url (418 stars, last pushed 21d ago), licensed MIT. It adds 94 tokens to every session and 1,894 once invoked, about $0.0004 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-09-22.
Other skills, from other repositories
reskin
Author a NEW skin for the reskinnable-demo app. A skin is a self-contained domain plugin under src/skins/ / that implements the frozen Skin contract (src/shell/skin-contract.ts) to swap the app's entire experience — brand, theme, layout, pages, tools, data, and agent — as a live sales demo. Use when the user says "add…
setup-slack-channel
Use for the PROVIDER half of getting a locally running CopilotKit Channels agent to answer in Slack, when no Slack app exists yet — setting up a Channels bot in Slack for the first time, creating the Slack app and its tokens, attaching it to a managed Intelligence Channel, or when a Channel reports setuprequired, sits…
copilotkit-channels
Use for the CODE half of a managed Intelligence Channel with Slack or Microsoft Teams: customising the Channel a CLI-scaffolded project already ships, or — for a project the CLI did not generate — writing the Channel declaration, the long-running host, and the awaited activation call. Teams provider setup is in scope…
copilotkit-cli
Use for the CopilotKit CLI — npx copilotkit@latest. Covers proving a project's wiring with verify before debugging anything by hand, scaffolding with create, signing in and selecting a hosted Intelligence project, agent-assisted onboarding of an existing app, generating type-safe agent ids, and importing thread…
channels-setup
Use when a developer wants to build their first CopilotKit Channels agent and get it answering in Slack or Microsoft Teams: "set up a channel", "connect my agent to Slack", "get my agent into Teams", or starting from nothing and wanting a working channel end to end. Covers the whole path: inspecting or scaffolding the…
inspector-workbench
Runs Inspector UI work on the standalone Threads state lab so the agent can see the overlay. Use when a CopilotKit employee asks an agent to fix, polish, add, or debug Inspector UI, chrome, panes, overlay actions, launcher, Home, Threads, Playground, Memory, or any visual behavior in @copilotkit/web-inspector. Don't…