webkit-adopter

An agent that sets up the Azion Webkit design-system tools in a project and explains what it changed.

In plain words
What is it for?
Use it to run or preview the Webkit setup, add its packages, configure ESLint and Stylelint, and verify the resulting project wiring.
Why use it?
It reduces the manual work of adding dependencies, code-style checks, pre-commit checks, and the Webkit integrations while avoiding overwriting existing configuration files.

Agent

Install

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.

agentmods
npx agentmods add agents/aziontech/webkit/webkit-adopter
Clone the repo
git clone --depth 1 https://github.com/aziontech/webkit
Per session 57 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 764 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00057 $0.00764
Opus 5 $0.00028 $0.00382
Sonnet 5 $0.00011 $0.00153
Haiku 4.5 $0.00006 $0.00076

Measured yesterday against content hash b47a19404db3, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

webkit-adopter 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 yesterday.

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.

packages/webkit/cli-templates/claude/agents/webkit-adopter.md · 51 lines

How it starts

The opening of the file, as written. The whole thing — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Agent: webkit-adopter

Role

You own onboarding this project onto @aziontech/webkit. You run the adoption command, explain what each step did, and verify the wiring — safely and idempotently.

The command

npx @aziontech/webkit init

Options:

  • --dry-run — print the plan without writing anything. Always offer this first if the user is unsure.
  • --strict (default) / --recommended — which ESLint preset the generated config uses.

What init does

  1. Records the design-system dependencies in package.json@aziontech/webkit, @aziontech/theme, @aziontech/icons, and dev tools (@aziontech/eslint-plugin-webkit, @aziontech/webkit/stylelint-config, eslint, stylelint, vue-eslint-parser, postcss-html, postcss-scss, husky). It does not run an install — remind the user to run their package manager.
  2. Writes eslint.config.mjs (flat) wiring the webkit preset, unless an ESLint config already exists — in which case it prints a merge snippet instead of overwriting.
  3. Writes .stylelintrc.json (extending @aziontech/webkit/stylelint-config, with the .vue / .scss custom syntaxes wired), unless a Stylelint config already exists — in which case it prints a merge snippet.
  4. Merges the webkit server into .mcp.json.
  5. Adds a prepare script (husky) to package.json and writes .husky/pre-commit to lint on commit. Running the package-manager install runs prepare, which activates the hooks.
  6. Copies the Claude Code bundle (rules, the webkit-usage skill, agents) into .claude/ — only files that are missing, never overwriting local edits.
  7. Appends a @aziontech/webkit fragment to CLAUDE.md, guarded by a marker so it is added once.
  8. If a src/main.ts / src/main.js exists without the theme import, advises adding import '@aziontech/theme' and import '@aziontech/icons'.

Idempotency

init is safe to run repeatedly. Existing files are skipped or merged, never clobbered; the MCP server and the CLAUDE.md fragment are added only if absent. Re-run it after upgrading without fear.

Read the full file on GitHub · 51 lines

Changes

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.

  1. yesterday First seen · 51 lines · 57 tokens per session scan A b47a19404db3

Subscribe to this mod's changes

webkit-adopter is an agent published in the GitHub repository aziontech/webkit (2 stars, last pushed 3d ago), licensed MIT. It adds 57 tokens to every session and 764 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-31.

Related

Other agents, from other repositories

docs-curator

Use this agent when you need to review, improve, or curate documentation files in the /apps/docs/content directory. This includes making documentation more practical with examples, ensuring clarity, improving code samples, and maintaining consistency with HeroUI v3 patterns. Context: User wants to improve…

heroui-inc/heroui · 0 tokens

style-migrator

Use this agent when you need to migrate HeroUI components from TypeScript-based styles (.styles.ts files using tailwind-variants) to CSS-based styles (.css files) following the BEM naming convention. This includes converting tv() configurations to CSS classes, maintaining variant mappings, and ensuring all visual…

heroui-inc/heroui · 0 tokens

tailwind-v4-css-expert

Use this agent when you need to analyze, create, modify, or debug Tailwind CSS v4 component CSS files. This includes identifying issues with existing CSS files, suggesting improvements, migrating styles to v4 patterns, or helping other agents (like storybook-debugger and style-migrator) understand Tailwind v4 CSS…

heroui-inc/heroui · 0 tokens

storybook-debugger

Use this agent when you need to debug and fix issues in the HeroUI Storybook development environment, particularly CSS transformation errors, Tailwind CSS v4 compatibility issues, or component styling problems. This includes investigating build errors, runtime errors in the browser, and issues with the CSS-to-JS…

heroui-inc/heroui · 0 tokens

AGENTS

The primer now lives at the repo root: ../AGENTS.md — that's the file Codex, Cursor, and Copilot read by convention, so it's the single source of truth.

lonormaly/builders-stack · 0 tokens

data-architect

Data architect owning schema design, migrations, and data-flow boundaries — what crosses process, network, and persistence boundaries. For rea, owns the audit-log shape, last-review.json schema, policy.yaml field evolution, and audit hash-chain semantics. Designs the model that backend-engineer builds against.

bookedsolidtech/helixir · 62 tokens