agentmods.dev

webkit: Skill for Claude Code

.claude/skills/echo-report/SKILL.md

echo-report is a skill for Claude Code from aziontech/webkit. It costs 36 tokens per session (1,079 once invoked), scanned A, original, MIT.

A final checker that rereads files created during a component build and compares them with the component specification. It uses a separate parser to check the Vue files, Storybook story, and optional Figma mapping.

In plain words
What is it for?
Use it as the final verification step after generating a component, its Storybook story, and its Figma mapping.
Why use it?
It catches missing or extra props, events, slots, stories, or mappings after other checks have run. Differences between the two checks are flagged for human review.

Skill for Claude Code

Written for Claude Code: PostToolUse hook event.

This is aziontech/webkit's own configuration. It tells Claude Code how to work on webkit itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything webkit configures →

not rated 3repo today A scan 36 tokens original MIT
View source ↗ aziontech/webkit
Reuse

Borrowing it

Nothing to install: this file belongs to aziontech/webkit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/aziontech/webkit/main/.claude/skills/echo-report/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/aziontech/webkit

Made for: Claude Code.

Wrote 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.

agentmods badge for echo-report

README.md
[![agentmods](https://agentmods.dev/badge/skills/aziontech/webkit/echo-report/github.svg)](https://agentmods.dev/skills/aziontech/webkit/echo-report)
Your own site
<a href="https://agentmods.dev/skills/aziontech/webkit/echo-report"><img src="https://agentmods.dev/badge/skills/aziontech/webkit/echo-report/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.

agentmods 80×15 button for echo-report

Your own site · 80×15
<a href="https://agentmods.dev/skills/aziontech/webkit/echo-report"><img src="https://agentmods.dev/badge/skills/aziontech/webkit/echo-report.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,079 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00036 $0.01079
Opus 5.5 $0.00014 $0.00432
Sonnet 5.5 $0.00007 $0.00216
Haiku 4.5 $0.00004 $0.00108

Measured 2mo ago against content hash 85159232457d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

echo-report 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 2mo 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.

.claude/skills/echo-report/SKILL.md · 77 lines

How it starts

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

Skill: echo-report

Purpose

After scaffolding + storybook + code-connect have written files, this skill re-reads them from disk, re-parses defineProps / defineEmits / defineSlots / story exports / .figma.ts mappings, and produces a diff against the spec. If validate-spec-compliance.mjs (the PostToolUse hook) and this skill disagree on any artifact, the run is marked degraded and a human is asked to review.

Two parsers agreeing is the precision boost.

When to invoke

  • Step 7 of /component-create, after code-connect-write (or its skip).

Inputs

  • The list of files the orchestrator's run log says were written.
  • The full text of .specs/<name>.md.
  • The output of validate-spec-compliance.mjs for the same files (passed by the orchestrator).

Workflow

  1. Re-read every <name>.vue, every sub-component .vue, the <Name>.stories.js, and (if present) <name>.figma.ts.
  2. Independent parsing. Do not call into _lib/spec.mjs. Parse with a hand-rolled regex/AST pass:
    • defineProps<{...}>() block → list of { name, type, optional, default }.
    • defineEmits<{ name: [args] }>() → list of { name, payload }.
    • defineSlots<{ name(...): unknown }>() → list of { name }.
    • defineOptions({ name: '...' }) → component name.
    • provide(<Key>InjectionKey, ...) / inject(<Key>InjectionKey) → composition marker.
    • Story file: export const <Name> names + their args.
    • .figma.ts: figma.connect(<Component>, '...', { props: {...} }) keys.
  3. Diff against spec.
    • Props in .vue ≠ spec.Props → block.
    • Events in .vue ≠ spec.Events → block.
    • Slots in .vue ≠ spec.Slots → block.
    • Sub-components: every <name>-<part>.vue matches spec.Sub-components.
    • Story exports ≠ spec.Stories → block.
    • .figma.ts enum keys ≠ spec.Props values → block.
  4. Animations cross-check. The spec's ## Motion & Animations section lists the expected animate-* / transition-* classes per state. Grep the .vue files:
    • Every animation class in the spec must appear at least once in the .vue.
    • Every animation class in the .vue must appear in the spec.
    • Each animate-* class on a transformable element must be paired with motion-reduce:animate-none or motion-reduce:transition-none (or have a same-line escape). Spec says _none_ → zero animate-* / transition-* classes allowed.
  5. Cross-check with the hook. Compare your diff with the validate-spec-compliance.mjs output. Same verdict → run continues. Different verdict → mark the run degraded and ask the user to investigate.
  6. Emit the final report using the structure in COMPONENT_REQUIREMENTS.md (Summary / Files created / Exports added / Tokens mapped / Theme gaps / Reused utilities / Pending items / Validation / Accessibility checklist / Usability checklist / Suggested next steps).

Read the full file on GitHub · 77 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. 2mo ago First seen · 77 lines · 36 tokens per session scan A 85159232457d

Subscribe to this mod's changes

echo-report is a skill published in the GitHub repository aziontech/webkit (3 stars, last pushed today), licensed MIT. It adds 36 tokens to every session and 1,079 once invoked, about $0.0001 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-31.

component-libraryfrontend-platformmonorepoui-architectureworkspace
Related

Other skills, from other repositories

monorepo-management

Sets up or audits a monorepo workspace: tool selection, package naming, shared tooling, inter-package dependencies, selective CI, and versioning strategy. Invoked when the user asks to set up a monorepo, add a workspace, or manage multiple packages in a single repository.

soulcodex/agentic · 63 tokens

bazel-monorepo-expert

Expert knowledge for managing large-scale Bazel monorepos with multiple services, shared libraries, and cross-cutting concerns. Use for workspace structure, visibility, and dependency management.

kinhluan/rules-quarkus-skills · 43 tokens

pnpm

Skill "pnpm" from pledgeandgrow/pledge-skills, covering pnpm documentation skill, key benefits, file index, quick start and install pnpm.

pledgeandgrow/pledge-skills · 31 tokens

data-dashboard

Build a dense, data-heavy screen - an analytics console or a trading terminal - with real charts drawn from tokens: candlestick, volume, depth, stacked area, waterfall, scatter, correlation matrix, donut, gauge, sparklines, heatmaps and order books. Use when the request is a dashboard, terminal, monitoring view, data…

plugin87/ux-ui-agent-skills · 113 tokens

critique

Adversarial design critique of the current work. Render it, look at it, and argue for rejection. Run after the gates are green, never instead of them.

plugin87/ux-ui-agent-skills · 37 tokens

fast-typescript-check

Keep www-sacred's TypeScript fast to type-check and fast to run. Use when touching the ASCII/canvas animation components (the only real per-frame code here), tightening type-check wall-clock, or auditing a change for runtime or compiler regressions. Scoped to this repo — a React 19 / Next.js 16 component library plus…

internet-development/www-sacred · 84 tokens