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/hemangjoshi37a/claude-code-frontend-dev/frontend-validatorgit clone --depth 1 https://github.com/hemangjoshi37a/claude-code-frontend-devWhat 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.00022 | $0.07448 |
| Opus 5 | $0.00011 | $0.03724 |
| Sonnet 5 | $0.00004 | $0.01490 |
| Haiku 4.5 | $0.00002 | $0.00745 |
Grade A, and why
frontend-validator 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 2d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 2d ago First seen · 1,164 lines · 22 tokens per session scan A f62f042185e8
frontend-validator is an agent published in the GitHub repository hemangjoshi37a/claude-code-frontend-dev (33 stars, last pushed 7mo ago), with no licence file. It adds 22 tokens to every session and 7,448 once invoked, about $0.0001 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-30.
Other agents, from other repositories
acceptance-tester
E2E acceptance testing agent — runs real-browser tests against web apps and reports structured results with blocking issues and suggested fixes. Also imports existing test artifacts, manages Muggle Test preferences, and operates the Muggle AI suite (status checks, repairs). Dispatch this agent when the team needs…
test-prepare-runner
Executes a fully-resolved Muggle Test prepare plan — detects what's listening, verifies env files, fresh-installs stale deps, starts approved services, smoke-tests, and returns the readiness table. Dispatched by the muggle-test-prepare skill after all user decisions are resolved; carries the opus pin so execution…
visual-walkthrough-builder
Renders the Muggle Test E2E visual walkthrough for a PR — assembles the E2eReport, runs muggle build-pr-section, and either posts to the PR (Mode A) or returns the rendered block to the dispatcher (Modes B/C). Dispatched by the muggle-pr-visual-walkthrough skill; carries its sonnet pin so the render runs on sonnet…
scorer
Simulates Phoenix algorithm scoring on X post drafts. Returns detailed signal analysis and composite scores.
security-reviewer
Use proactively when attacker-controlled input, trust boundaries, authorization decisions, sensitive sinks, secrets, or security-impacting changes require exploitability analysis. Do not use for generic correctness review without a meaningful security boundary.
html-reader
Background agent for reading ar5iv.org HTML papers using agent-browser CLI.