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/aziontech/webkit/echo-reportnpx skills add aziontech/webkit --skill echo-reportgit clone --depth 1 https://github.com/aziontech/webkitWhat 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.00036 | $0.01079 |
| Opus 5 | $0.00018 | $0.00540 |
| Sonnet 5 | $0.00007 | $0.00216 |
| Haiku 4.5 | $0.00004 | $0.00108 |
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 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.
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, aftercode-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.mjsfor the same files (passed by the orchestrator).
Workflow
- Re-read every
<name>.vue, every sub-component.vue, the<Name>.stories.js, and (if present)<name>.figma.ts. - 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 + theirargs. .figma.ts:figma.connect(<Component>, '...', { props: {...} })keys.
- 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>.vuematches spec.Sub-components. - Story exports ≠ spec.Stories → block.
.figma.tsenum keys ≠ spec.Props values → block.
- Props in
- Animations cross-check. The spec's
## Motion & Animationssection lists the expectedanimate-*/transition-*classes per state. Grep the.vuefiles:- Every animation class in the spec must appear at least once in the
.vue. - Every animation class in the
.vuemust appear in the spec. - Each
animate-*class on a transformable element must be paired withmotion-reduce:animate-noneormotion-reduce:transition-none(or have a same-line escape). Spec says_none_→ zeroanimate-*/transition-*classes allowed.
- Every animation class in the spec must appear at least once in the
- Cross-check with the hook. Compare your diff with the
validate-spec-compliance.mjsoutput. Same verdict → run continues. Different verdict → mark the rundegradedand ask the user to investigate. - 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).
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.
- yesterday First seen · 77 lines · 36 tokens per session scan A 85159232457d
echo-report is a skill published in the GitHub repository aziontech/webkit (2 stars, last pushed 4d ago), licensed MIT. It adds 36 tokens to every session and 1,079 once invoked, about $0.0002 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.
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.
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.
pnpm
Skill "pnpm" from pledgeandgrow/pledge-skills, covering pnpm documentation skill, key benefits, file index, quick start and install pnpm.
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…
port-sacred-terminal-ui-to-typescript-cli
Take a React Window.tsx (or any sacred component) and produce a terminal CLI screen written in TypeScript that uses Simulacrum — the sacred CLI framework in scripts/cli/lib/.
port-sacred-terminal-ui-to-react-using-same-conventions
Take a CLI screen written for Simulacrum — the sacred CLI framework (scripts/cli/templates/.ts or scripts/python/templates/.py) — and produce a React component that lives inside components/examples/ (or components/) using only sacred's existing primitives — Window, Card, SimpleTable, ActionButton, RowSpaceBetween…