validate-frontend

A command for checking an online shop's frontend before it goes live.

In plain words
What is it for?
Use it for a pre-release check of an e-commerce website.
Why use it?
It helps find frontend problems before they affect customers in production.

Command for Claude Code

Install

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.

agentmods
npx agentmods add commands/lroy-stack/ai-pod-store/validate-frontend
Clone the repo
git clone --depth 1 https://github.com/lroy-stack/ai-pod-store

Made for: Claude Code.

Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 11,111 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 2 findings. Scan, not verified.
Origin unknown 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 $0.00011 $0.11111
Opus 5 $0.00005 $0.05555
Sonnet 5 $0.00002 $0.02222
Haiku 4.5 $0.00001 $0.01111

Measured 2d ago against content hash 266f0e439d20, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade C, and why

validate-frontend scanned grade C with 2 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

- Command injection en design params: `; rm -rf /` → validacion rechaza

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -s -o /dev/null -w "%{http_code}" http://localhost:3000/api/health && echo " /api/health"
project/.claude/commands/validate-frontend.md · 1,064 lines

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.

Read it on GitHub

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. 2d ago First seen · 1,064 lines · 11 tokens per session scan C 266f0e439d20

Subscribe to this mod's changes

validate-frontend is a command published in the GitHub repository lroy-stack/ai-pod-store (5 stars, last pushed 3mo ago), with no licence file. It adds 11 tokens to every session and 11,111 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.