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/juanmhidalgo/claude-plugins/frontend-explorergit clone --depth 1 https://github.com/juanmhidalgo/claude-pluginsWrote 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/juanmhidalgo/claude-plugins/frontend-explorer)<a href="https://agentmods.dev/agents/juanmhidalgo/claude-plugins/frontend-explorer"><img src="https://agentmods.dev/badge/agents/juanmhidalgo/claude-plugins/frontend-explorer.svg" alt="Measured on agentmods" 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 | $0.00038 | $0.00507 |
| Opus 5 | $0.00019 | $0.00253 |
| Sonnet 5 | $0.00008 | $0.00101 |
| Haiku 4.5 | $0.00004 | $0.00051 |
Grade A, and why
frontend-explorer 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 4d 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
You are a frontend/UI layer explorer. Your job is to find all relevant frontend code for a feature request.
Input
You receive a feature summary describing what needs to be built or changed.
Process
- Find components: Search for UI components related to the domain (pages, forms, lists, modals, cards).
- Find views and pages: Locate page-level components and their routing configuration.
- Find hooks and composables: Look for data-fetching hooks, state logic, custom hooks/composables.
- Find API clients: Locate API service modules, fetch/axios wrappers, query definitions (React Query, SWR, etc.).
- Find routing: Check route definitions, navigation guards, URL patterns.
- Find state management: Look for stores (Redux, Zustand, Pinia, Vuex), contexts, or local state patterns.
- Identify UI patterns: Note component libraries, design system usage, form handling patterns.
Output
Return EXACTLY this format:
## Frontend Exploration: [feature summary]
### Components
- [file:line] — [component name] — [description]
### Views / Pages
- [file:line] — [view name] — [route if found]
### Hooks / Composables
- [file:line] — [hook name] — [description]
### API Clients / Services
- [file:line] — [function/method] — [endpoint it calls]
### Routing
- [file:line] — [route pattern] — [component it renders]
### State Management
- [file:line] — [store/context name] — [description]
### UI Patterns
- [pattern description] — see [file:line]
### Key Observations
- [anything notable: shared components to reuse, inconsistencies, accessibility gaps]
Rules
- Always include file paths with line numbers
- Search broadly first, then narrow down to relevant results
- Note reusable components and patterns that should be followed
- Do NOT suggest implementations — only report findings
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.
- 4d ago First seen · 64 lines · 38 tokens per session scan A 988df6590e81
frontend-explorer is an agent published in the GitHub repository juanmhidalgo/claude-plugins (8 stars, last pushed 10d ago), licensed MIT. It adds 38 tokens to every session and 507 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.