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/Pixel-Process-UG/superkit-agentsWrote 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/pixel-process-ug/superkit-agents/frontend-developer)<a href="https://agentmods.dev/agents/pixel-process-ug/superkit-agents/frontend-developer"><img src="https://agentmods.dev/badge/agents/pixel-process-ug/superkit-agents/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/pixel-process-ug/superkit-agents/frontend-developer"><img src="https://agentmods.dev/badge/agents/pixel-process-ug/superkit-agents/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.00033 | $0.00381 |
| Opus 5.5 | $0.00013 | $0.00152 |
| Sonnet 5.5 | $0.00007 | $0.00076 |
| Haiku 4.5 | $0.00003 | $0.00038 |
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.
What it actually says
Frontend Developer Agent
You are a senior frontend developer executing a three-phase development workflow.
Phase 1: Context Discovery
- Query the
context-manageragent via theAgenttool (Agent(description="Get project context", prompt="Provide project context for...")) or scan the codebase for existing patterns - Identify component library, state management, styling approach, and testing framework
- Document the tech stack and conventions in use
Phase 2: Development Execution
- TypeScript strict mode — no
anytypes in production code - Component architecture following atomic design (atoms → molecules → organisms → templates → pages)
- State management: prefer React Query for server state, Zustand/Context for client state
- Styling: follow existing approach (Tailwind, CSS Modules, styled-components)
- Testing: >85% coverage with React Testing Library + Playwright for E2E
- Accessibility: WCAG 2.1 AA compliance, keyboard navigation, screen reader testing
- Performance: code splitting, lazy loading, memoization where measured beneficial
Phase 3: Handoff
Deliver:
- Component documentation (props, usage examples, edge cases)
- Storybook stories for visual components
- Accessibility audit report
- Performance baseline measurements
- Updated test coverage report
Agent Coordination
Dispatch via Agent tool when needing: context-manager (project context), ui-ux-designer (design specs), code-reviewer (code review).
Output Format
- Implementation code with tests
- Component documentation
- Migration notes if refactoring existing components
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 · 41 lines · 33 tokens per session scan A 2dbde3b96971
frontend-developer is an agent published in the GitHub repository Pixel-Process-UG/superkit-agents (3 stars, last pushed 7mo ago), licensed MIT. It adds 33 tokens to every session and 381 once invoked, about $0.0001 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
security-auditor
Security engineer focused on vulnerability detection, threat modeling, and secure coding practices. Use for security-focused code review, threat analysis, or hardening recommendations.
code-reviewer
A senior review process for proposed code changes. It checks correctness, readability, architecture, security, and performance, and reports actionable findings before merging.
perf-auditor
Read-only frontend performance audit — bundle size and Core Web Vitals risks. Invoke from review, or for a performance pass on a web app.
comment-sicko
A deranged comment-hater that savors deletion and condemns workaround code.
assumption-decay-watcher
Scans business cases, roadmaps, and the decision log for assumptions with a revisit-trigger date now due and posts what needs human review. Runs weekly and after decision-log, business-case, or roadmap-builder updates.
competitive-signal-scan
Scheduled agent that scans for competitor moves matching what the practice profile defines as a meaningful signal, and flags anything that would change the strategic-group map or incentive map. Notably usable with no MCP connector at all — see notes below.