Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/asmyshlyaev177/state-in-urlnpx agentmods add skills/asmyshlyaev177/state-in-url/astro-setupWrote 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/astro-setup)<a href="https://agentmods.dev/skills/asmyshlyaev177/state-in-url/astro-setup"><img src="https://agentmods.dev/badge/skills/asmyshlyaev177/state-in-url/astro-setup/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/astro-setup"><img src="https://agentmods.dev/badge/skills/asmyshlyaev177/state-in-url/astro-setup.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.00102 | $0.01950 |
| Opus 5.5 | $0.00041 | $0.00780 |
| Sonnet 5.5 | $0.00020 | $0.00390 |
| Haiku 4.5 | $0.00010 | $0.00195 |
Grade A, and why
astro-setup 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 — 205 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 — Astro
Two shapes of Astro project, two tools:
| Project | Use | Runs |
|---|---|---|
React islands (@astrojs/react) |
useUrlState from state-in-url/astro |
In the island, on the server render and in the browser |
Preact islands (@astrojs/preact, compat: true) |
the same useUrlState |
the same, through preact/compat |
| No client framework | decodeState / encodeState from state-in-url/encodeState |
In .astro frontmatter, per request |
Astro has no client-side router by default. The hook writes the URL with window.history (replaceState by default, pushState with replace: false) and reads it back on back/forward, on its own writes, and on any other pushState/replaceState on the page.
Setup: React islands
// src/state.ts — module scope, one object, imported by every island that shares it
type FiltersState = { sort: 'name' | 'date'; page: number };
export const FILTERS_STATE: FiltersState = { sort: 'name', page: 1 };
// src/components/Filters.tsx
import { useUrlState } from 'state-in-url/astro';
import { FILTERS_STATE } from '../state';
export function Filters({ searchParams }: { searchParams?: Record<string, string> }) {
const { urlState, setUrl } = useUrlState(FILTERS_STATE, { searchParams });
return <button onClick={() => setUrl({ page: urlState.page + 1 })}>Next</button>;
}
---
// src/pages/index.astro
import { Filters } from '../components/Filters';
// A plain object: island props are serialized, URLSearchParams is not.
const searchParams = Object.fromEntries(Astro.url.searchParams);
---
<Filters client:load searchParams={searchParams} />
The page must be rendered on demand — output: 'server', or export const prerender = false on the page — and either way an adapter must be configured (@astrojs/node, @astrojs/vercel, …); on Astro's default static output the build fails. Only then does Astro.url.searchParams hold the request's query. A prerendered page has no request, so searchParams is {} and the island fills its state in the browser after hydration.
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 · 205 lines · 102 tokens per session scan A 3d40c06d535f
astro-setup is a skill published in the GitHub repository asmyshlyaev177/state-in-url (418 stars, last pushed 21d ago), licensed MIT. It adds 102 tokens to every session and 1,950 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…