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/skb3002/agenthub/frontend-specialistgit clone --depth 1 https://github.com/SKB3002/agenthubWrote 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/skb3002/agenthub/frontend-specialist)<a href="https://agentmods.dev/agents/skb3002/agenthub/frontend-specialist"><img src="https://agentmods.dev/badge/agents/skb3002/agenthub/frontend-specialist.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.1 | $0.00068 | $0.06543 |
| Opus 5 | $0.00034 | $0.03272 |
| Sonnet 5 | $0.00014 | $0.01309 |
| Haiku 4.5 | $0.00007 | $0.00654 |
Grade A, and why
frontend-specialist 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 6d 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
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 6d ago First seen · 611 lines · 68 tokens per session scan A 65165f79d3a8
frontend-specialist is an agent published in the GitHub repository SKB3002/agenthub (3 stars, last pushed 4mo ago), with no licence file. It adds 68 tokens to every session and 6,543 once invoked, about $0.0003 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-reviewer
Frontend-focused code review for React applications. Checks accessibility, performance, React anti-patterns, and security. Lighter than the full reviewer — only examines frontend code.
page-builder
Builds ONE page or major section of a website end-to-end — React components, text content, mock data, media generation/sourcing (images, video, icons), Tailwind styling, and GSAP/CSS animations. Multiple page-builder instances run in parallel, each handling a different page. Receives its page spec from the design…
scaffold-builder
Sets up the project scaffold for a web design — Vite + React + TypeScript project initialization, Tailwind CSS configuration, global styles from design tokens, shared components (navigation, footer, layout), and shared media assets (logo, product images reused across pages). Runs before page-builder agents to…
visual-fixer-app
Final app-wide visual check after per-page visual fixers complete — does a quick crawl of ALL pages to catch cross-page issues, shared component problems (Navigation, Footer, Layout), and inconsistencies between pages. Fixes shared file issues that per-page fixers could not touch. Context: All per-page visual fixers…
assembler
Wires together individually-built pages into a complete website — React Router setup, shared navigation state, cross-page consistency, page transitions, and final integration. Runs after all page-builder agents complete. Context: All pages are built, need to wire them together user: "Assemble the website. Pages: Home…
frontend-developer
Use when building complete frontend applications across React, Vue, and Angular frameworks requiring multi-framework expertise and full-stack integration.