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.
curl -O https://raw.githubusercontent.com/aziontech/webkit/main/.claude/agents/echo-reporter.mdgit clone --depth 1 https://github.com/aziontech/webkitWrote 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/agents/aziontech/webkit/echo-reporter)<a href="https://agentmods.dev/agents/aziontech/webkit/echo-reporter"><img src="https://agentmods.dev/badge/agents/aziontech/webkit/echo-reporter/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/agents/aziontech/webkit/echo-reporter"><img src="https://agentmods.dev/badge/agents/aziontech/webkit/echo-reporter.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.00045 | $0.00474 |
| Opus 5.5 | $0.00018 | $0.00190 |
| Sonnet 5.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 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.
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.
- 2mo ago First seen · 38 lines · 45 tokens per session scan A 299fae37d636
echo-reporter is an agent published in the GitHub repository aziontech/webkit (3 stars, last pushed today), licensed MIT. It adds 45 tokens to every session and 474 once invoked, about $0.0002 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.
Other agents, from other repositories
swe-reviewer
Audits code, interface component source, and scenario bindings in named projects against the adopted standards, including test-first evidence and regression tests, and returns rated findings without modifying anything.
pdf-to-md-checker
Compares a converted Markdown file with its source PDF across seven fidelity dimensions and returns rated findings without editing either file.
pr-review-checker
Checks one pinned change for the pr-review family by coordinating one review pass: after the lens checkers report, it deduplicates, re-categorizes, filters, verifies, and rates raw findings for criticality, then publishes the one review bound to the pinned head, editing no file.
pr-review-docs-checker
Reviews one pinned change for the documentation discipline, judging substantive completeness, clarity, mode fit, drift from the code, accessibility, and whether the change description matches the diff, and returns anchored findings.
pr-review-fixer
Executes PR Review Propagation on a frozen review ledger, answering each blocking row on one change with a fix, a reasoned reject, or a deferral, tagging each answer's cause, and committing fixes only to the change's own branch.
pr-review-governance-checker
Reviews one pinned change for the governance discipline, checking mechanical conformance to rules the repository documents, such as naming, structure, and required files and sections, and returns anchored findings.