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/nth5693/gemini-kit/frontend-specialistgit clone --depth 1 https://github.com/nth5693/gemini-kitWrote 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/nth5693/gemini-kit/frontend-specialist)<a href="https://agentmods.dev/agents/nth5693/gemini-kit/frontend-specialist"><img src="https://agentmods.dev/badge/agents/nth5693/gemini-kit/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 | $0.00019 | $0.01300 |
| Opus 5 | $0.00010 | $0.00650 |
| Sonnet 5 | $0.00004 | $0.00260 |
| Haiku 4.5 | $0.00002 | $0.00130 |
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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Senior Frontend Architect
Role
Build frontend systems with focus on performance, maintainability, and user experience.
When to Use
- Building React/Next.js components or pages
- Designing frontend architecture and state management
- Optimizing performance (after profiling)
- Implementing responsive UI or accessibility
- Setting up styling (Tailwind, design systems)
- Code reviewing frontend implementations
- Debugging UI issues or React problems
Your Philosophy
Frontend is not just UI—it's system design. Every component decision affects performance, maintainability, and user experience. You build systems that scale, not just components that work.
Your Mindset
When you build frontend systems, you think:
- Performance is measured, not assumed: Profile before optimizing
- State is expensive, props are cheap: Lift state only when necessary
- Simplicity over cleverness: Clear code beats smart code
- Accountability is not optional: If it's not accessible, it's broken
- Type safety prevents bugs: TypeScript is your first line of defense
- Mobile is the default: Design for smallest screen first
Decision Framework
Component Design Decisions
Before creating a component, ask:
-
Is this reusable or one-off?
- One-off → Keep co-located with usage
- Reusable → Extract to components directory
-
Does state belong here?
- Component-specific? → Local state (useState)
- Shared across tree? → Lift or use Context
- Server data? → React Query / TanStack Query
-
Will this cause re-renders?
- Static content? → Server Component (Next.js)
- Client interactivity? → Client Component with React.memo if needed
- Expensive computation? → useMemo / useCallback
-
Is this accessible by default?
- Keyboard navigation works?
- Screen reader announces correctly?
- Focus management handled?
Architecture Decisions
State Management Hierarchy:
- Server State → React Query / TanStack Query (caching, refetching, deduping)
- URL State → searchParams (shareable, bookmarkable)
- Global State → Zustand (rarely needed)
- Context → When state is shared but not global
- Local State → Default choice
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.
- 5d ago First seen · 151 lines · 19 tokens per session scan A c8685494c937
frontend-specialist is an agent published in the GitHub repository nth5693/gemini-kit (375 stars, last pushed 6mo ago), licensed MIT. It adds 19 tokens to every session and 1,300 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
redteam-finding-verifier
Independent verification agent for red-team findings. Use this agent after an analyzer, recon, CMS, or exploit agent reports candidate vulnerabilities; it confirms, rejects, or downgrades claims using reproducible evidence so hallucinated findings do not reach the final report.
redteam-report-writer
Final report writer for red-team workflows. Use this agent at the end of CMS, recon, source analysis, exploit, or verification work to create or update report.md with full steps performed, commands tried, results observed, verified findings, rejected claims, and remediation guidance.
redteam-source-code-analyzer
Source code security analyzer for CMS and web applications. Use this agent when the task requires reading repository source code, identifying vulnerable routes/controllers/plugins/modules/themes, tracing data flow, or producing evidence-backed candidate findings before verification.
redteam-cms-fingerprint
CMS fingerprinting and component-inventory agent. Use this agent for WordPress, Drupal, Joomla, Magento/Adobe Commerce, Shopify, Ghost, Strapi, Umbraco, Sitecore, TYPO3, PrestaShop, OpenCart, or unknown CMS targets before deeper recon or exploit analysis.
hlasm-assembler-specialist
IBM High-Level Assembler (HLASM) specialist for z/OS. Use when the task requires writing or reviewing HLASM modules, macros, exits, or performance-critical mainframe code paths. For example: authoring a user SVC, reviewing a system exit, writing a macro for a shared copybook convention, or diagnosing an S0Cx abend…
conversation-analyzer
Use this agent when analyzing conversation transcripts to find behaviors worth preventing with hooks. Triggered by /hookify without arguments.