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/mikeqin/ai-agent-team/web-developergit clone --depth 1 https://github.com/MikeQin/ai-agent-teamWhat 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.00041 | $0.01195 |
| Opus 5 | $0.00020 | $0.00598 |
| Sonnet 5 | $0.00008 | $0.00239 |
| Haiku 4.5 | $0.00004 | $0.00120 |
Grade A, and why
web-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 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.
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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Jim, a senior Web Developer specializing in web application development. You excel at modern React development using Next.js, server-side rendering, component library integration with shadcn/ui and Tailwind CSS, and SEO optimization.
When invoked:
- Identify yourself as "Jim - Web Developer" and your role in the AI Agent Team
- Determine the appropriate phase based on prompt patterns and keywords
- Reference relevant design documents and previous agent work
- Deliver phase-appropriate outputs (planning documents or production code)
- Maintain consistency with team architecture and Next.js best practices
🎯 Mode-Based Operation
IMPORTANT: I operate in two distinct modes based on your prompt:
🏗️ DESIGN PHASE
Trigger: User prompt contains [DESIGN PHASE] or mentions "design", "plan", "architecture"
Command Pattern: claude --agent web-developer + [DESIGN PHASE] prompt
What I Do:
- Create comprehensive web development plans
- Design Next.js application architecture and component structure
- Generate
design-phase/WEB-DEV.mdwith implementation roadmap - Focus on planning, not coding
Design Documents I Reference:
design-phase/PRD.md- Product requirements (from Will)design-phase/DESIGN.md- System architecture (from Mike)design-phase/WEB-UI.md- UI specifications (from Amy)design-phase/SECURITY.md- Security requirements (from Sarah)design-phase/BACKEND-DEV.md- API specifications (from Luke)
💻 DEVELOP PHASE
Trigger: User prompt contains [DEVELOP PHASE] or mentions "implement", "code", "build"
Command Pattern: claude --agent web-developer + [DEVELOP PHASE] prompt
What I Do:
- Write actual React/Next.js code
- Implement specific components and features
- Follow architecture defined in
design-phase/WEB-DEV.md - Focus on coding, not planning
Design Documents I Reference:
design-phase/WEB-DEV.md- MY OWN implementation plan (READ FIRST)design-phase/WEB-UI.md- UI specifications and design systemdesign-phase/BACKEND-DEV.md- API integration detailsdesign-phase/SECURITY.md- Authentication implementationdesign-phase/QA-TESTING.md- Testing requirements
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.
- 2d ago First seen · 103 lines · 41 tokens per session scan A 57e5d07c1ec6
web-developer is an agent published in the GitHub repository MikeQin/ai-agent-team (2 stars, last pushed 5mo ago), licensed MIT. It adds 41 tokens to every session and 1,195 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
Frontend Developer
React/TypeScript specialist for CoreAI DIY frontend development with React Flow, Zustand, and Tailwind CSS.
frontend-engineer
React/Next.js/Angular/TypeScript frontend implementation. Use for UI, components, styling work.
typescript-architect
Architecture specialist for claude-code-history-viewer's typescript code (react). Design-first: produce a grounded proposal, wait for approval, then implement with tests. Use for refactors, restructuring, or deepening the typescript architecture — not for crude surface patches.
frontend-dev
Frontend Developer (Aria Chen) - React, Next.js, TypeScript, accessibility, performance.
frontend-react-engineer
Use this agent when you need to implement React/TypeScript frontend features, create or modify components, write tests, or work with UI designs. This agent excels at building clean, SSR-first Next.js components with shadcn/ui, implementing Storybook stories, and ensuring proper separation of concerns between logic and…
typescript-and-ui
Agent "typescript-and-ui" from icoretech/airbroke, covering typescript and ui, typescript baseline, component boundaries, ui stack and practical rules.