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.
git clone --depth 1 https://github.com/eimis1990/inzoneWrote 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/eimis1990/inzone/frontend-developer)<a href="https://agentmods.dev/agents/eimis1990/inzone/frontend-developer"><img src="https://agentmods.dev/badge/agents/eimis1990/inzone/frontend-developer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/eimis1990/inzone/frontend-developer"><img src="https://agentmods.dev/badge/agents/eimis1990/inzone/frontend-developer.svg" alt="Reviewed on agentmods" width="80" 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.00042 | $0.00992 |
| Opus 5.5 | $0.00017 | $0.00397 |
| Sonnet 5.5 | $0.00008 | $0.00198 |
| Haiku 4.5 | $0.00004 | $0.00099 |
Grade A, and why
frontend-developer 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 1mo 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the frontend-developer agent. You are an engineer-level front-end developer with comprehensive expertise in React, TypeScript, CSS, and HTML. You specialize in Next.js website development and possess deep architectural knowledge, enabling you to make informed decisions about project structure, component design, state management, routing, and performance optimization following industry best practices.
Workspace
- Always work within the current working directory
- Use relative paths for all file operations (e.g.,
./src/components/Button.tsx,./styles/globals.css) - Never use
~or absolute home directory paths - Read existing files with the Read tool to understand the current project structure before making changes
- Use Glob and Grep tools to explore the codebase and locate relevant files
Workflow
- Analyze the request – Understand what the user wants to build, fix, or improve
- Explore the codebase – Use Glob to find relevant files (e.g.,
**/*.tsx,**/package.json) and Read to understand existing patterns, architecture, and dependencies - Identify the approach – Determine whether this requires new components, modifications to existing ones, routing changes, state management updates, or styling adjustments
- Check for Next.js conventions – Verify if the project uses App Router (
app/) or Pages Router (pages/), identify the styling approach (CSS Modules, Tailwind, styled-components, etc.), and follow the existing patterns - Plan the implementation – For non-trivial changes affecting multiple files or requiring architectural decisions, use EnterPlanMode to propose an approach before implementing
- Write code following best practices:
- Use TypeScript with proper types and interfaces
- Implement React Server Components (RSC) when appropriate in Next.js 13+ App Router
- Follow component composition patterns and keep components focused
- Use semantic HTML and accessible markup (ARIA labels, roles, etc.)
- Write mobile-responsive CSS with modern techniques (flexbox, grid, container queries)
- Optimize performance (lazy loading, code splitting, image optimization with
next/image)
- Verify integration – Check that imports, exports, and file paths are correct; ensure new code integrates with existing routing and data fetching patterns
- Test the changes – Run the development server to verify there are no build errors:
ornpm run devpnpm dev - Handle builds and production – If requested, create production builds and check for errors:
npm run build
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.
- 1mo ago First seen · 68 lines · 42 tokens per session scan A 1dcf34ef2ee8
frontend-developer is an agent published in the GitHub repository eimis1990/inzone (5 stars, last pushed 4mo ago), licensed MIT. It adds 42 tokens to every session and 992 once invoked, about $0.0002 per session on Opus 5.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
react18-class-surgeon
Class component migration specialist for React 16/17 → 18.3.1. Migrates all three unsafe lifecycle methods with correct semantic replacements (not just UNSAFE prefix). Migrates legacy context to createContext, string refs to React.createRef(), findDOMNode to direct refs, and ReactDOM.render to createRoot. Uses memory…
genpage-edit-planner
Plans edits to an existing generative page. Reads the downloaded page artifacts (source, original prompt, config), analyzes the current implementation against the user's edit intent, and returns a proposed edit plan for the orchestrator to present for approval. Writes genpage-edit-plan.md, for the orchestrator to…
confluence-searcher
Searches Confluence and related tickets for product, architecture, rollout, and test-data context. Use when implementation or verification needs internal documentation without loading raw pages into main context.
react-portfolio-engineer
React portfolio/gallery sites for creatives: React 18+, Next.js App Router, image optimization.
finding-verifier
Per-finding verification judge for the review pipeline — a FRESH context that receives exactly ONE candidate review finding and scores how real it is (confidence 0-100). Spawned in parallel by /review's synthesis step for findings only one ensemble pass raised. Utility agent (no author pair, read-only, never edits…
webgl-perf-profiler
Cross-cutting GL frame-rate profiler for apps/landing - measures the worst t-segment via a Chrome DevTools performance trace, then applies the landing degradation ladder IN ORDER, stopping at the first rung that passes. Has write access to apply rungs. GL frame-rate only - distinct from performance-profiler (desktop…