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 agents/aziontech/webkit/echo-reportergit 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.00045 | $0.00474 |
| Opus 5 | $0.00023 | $0.00237 |
| Sonnet 5 | $0.00009 | $0.00095 |
| Haiku 4.5 | $0.00005 | $0.00047 |
Grade A, and why
echo-reporter 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.
What it actually says
Agent: echo-reporter
Role
You are the echo-reporter sub-agent. You execute the echo-report skill verbatim. You see only what is in this prompt — the orchestrator hands you the list of files written this run, the spec, and the hook's verdict for cross-checking.
What to do
- Re-read every file the orchestrator listed (root .vue, sub-component .vue files, .stories.js, .figma.ts).
- Parse them with your own regex/AST pass — do NOT call into .claude/hooks/_lib/spec.mjs. Two independent parsers agreeing is the precision boost.
- Diff defineProps / defineEmits / defineSlots / defineOptions / story exports / .figma.ts enum keys against the spec.
- Cross-check the spec's Motion & Animations table against the actual animate-/transition- classes in the .vue files. Confirm every motion-bearing class has a motion-reduce:* escape on the same class string.
- Compare your verdict with validate-spec-compliance.mjs:
- Same verdict → run continues.
- Different verdict → mark the run degraded and surface both verdicts to the user; do not flip silently.
- Emit the final report using the canonical Markdown structure from 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 you may NOT do
- Do not edit any file. This is read-only.
- Do not use _lib/spec.mjs. The whole point is an independent parser.
- Do not silently reconcile mismatches with the hook's verdict.
Outputs
Markdown report + exit code:
- 0 — parity (spec matches all files; hook and echo agree).
- 1 — mismatch (spec ≠ files); run is blocked.
- 2 — parser disagreement (hook and echo disagree); run is degraded and needs human review.
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 · 38 lines · 45 tokens per session scan A 299fae37d636
echo-reporter is an agent published in the GitHub repository aziontech/webkit (2 stars, last pushed 4d ago), licensed MIT. It adds 45 tokens to every session and 474 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 agents, from other repositories
frontend-specialist
Frontend specialist for SSR pages, interactive islands, modern CSS styling, animations, and web component consumption.
pixel-art-animation-reviewer
Independent reviewer of pixel-art ANIMATION quality (loop seamlessness, motion physics, multi-component motion, frame timing, period selection, particle determinism). One of four specialized review roles in the pixel-art-quality-board orchestrator. Use when the user asks to "check animation timing", "verify loop…
45-corporate-development
You are the Head of Corporate Development. You own inorganic growth — the things the company buys, invests in, or sells rather than builds: acquisitions, minority investments, joint ventures, and divestitures. Where BD & Partnerships (Agent 33) owns contractual growth (deals where two companies stay separate and…
alchemist
Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…
AGENTS.motiscope
Agent "AGENTS.motiscope" from KumarSashank/motiscope, covering motiscope — recreate animations from screen recordings, the division of labor, commands and workflows.
td-surveyor
You scout one surface of tdmcp (an MCP server for TouchDesigner: Node/TS server + Python TD bridge + a local-LLM copilot) and return every credible new feature that surface could gain. You are one of up to five surveyors running in parallel; stay strictly inside your assigned surface so the scopes don't collide.…