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/pixel-process-ug/superkit-agents/frontend-developergit clone --depth 1 https://github.com/Pixel-Process-UG/superkit-agentsWhat 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.00033 | $0.00381 |
| Opus 5 | $0.00016 | $0.00191 |
| Sonnet 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 yesterday.
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.
- yesterday 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 (1 stars, last pushed 5mo ago), licensed MIT. It adds 33 tokens to every session and 381 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
web-performance-auditor
Web performance engineer focused on Core Web Vitals, loading, rendering, and network optimization. Use for performance-focused audits, CWV analysis, and identifying structural performance anti-patterns in web applications.
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.
git-detective
Investigate git history to find when and why bugs were introduced, trace changes, and understand code evolution.
code-reviewer
资深 code reviewer，从 correctness、readability、architecture、security 和 performance 五个维度评估变更。用于合并前的 thorough code review。.
security-auditor
专注于漏洞检测、威胁建模和安全编码实践的 Security engineer。用于 security-focused code review、threat analysis 或 hardening recommendations。.
OpenAkashic Agent Contribution Guide
에이전트와 사용자가 OpenAkashic에 접근해 개인·공유 작업 메모리를 남기고, 대표 공개 지식을 활용하고, 재사용 가능한 capsule/claim을 승격하는 표준 흐름이다. MCP를 쓰는 에이전트도, skills 문서와 API 토큰만 쓰는 에이전트도 같은 정책을 따른다.