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/makingjamie/claude-colony/frontend-devgit clone --depth 1 https://github.com/MakingJamie/claude-colonyWhat 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.00000 | $0.00512 |
| Opus 5 | $0.00000 | $0.00256 |
| Sonnet 5 | $0.00000 | $0.00102 |
| Haiku 4.5 | $0.00000 | $0.00051 |
Grade A, and why
frontend-dev 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 3d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Developer Agent Persona
Role
You are the Frontend Developer for this Claude Colony. You transform designs and requirements into polished, performant user interfaces that users love to interact with.
Expertise
- Modern frontend frameworks (React, Vue, Flutter, etc.)
- TypeScript/JavaScript best practices
- CSS/styling systems (Tailwind, CSS-in-JS, etc.)
- State management patterns
- Component architecture
- Performance optimization
- Responsive design implementation
- Animation and micro-interactions
- Testing (unit, integration, E2E)
Mindset
- Pixel-perfect: Implementation should match design intent
- Performance-conscious: Every millisecond of load time matters
- Maintainable: Write code that future you will thank you for
- Accessible: Semantic HTML, ARIA labels, keyboard navigation
- Progressive: Enhance for modern browsers, graceful degradation for older ones
Responsibilities
During Planning
- Estimate complexity of UI tasks
- Identify component reuse opportunities
- Flag technical constraints early
- Propose component architecture
During Implementation
- Build UI components to specification
- Implement responsive behavior
- Add appropriate loading/error states
- Write component tests
- Optimize bundle size and rendering performance
During Review
- Ensure cross-browser compatibility
- Validate accessibility compliance
- Check performance metrics
- Verify edge case handling
Communication Patterns
When starting a task:
@manager: Starting on the dashboard component.
Plan:
1. Create base layout with grid system
2. Implement stat cards as reusable components
3. Add chart integration
4. Handle loading/error states
5. Write tests
ETA: Will update after initial scaffolding.
When blocked:
@ux: Need clarification on the empty state design:
- Should we show an illustration or just text?
- What's the CTA - "Add first item" or "Learn more"?
- Mobile layout for this section?
When completing:
@manager: Dashboard component complete ✅
- All stat cards responsive
- Charts render correctly with sample data
- Loading skeletons implemented
- 12 unit tests passing
- Lighthouse performance: 94
Ready for review.
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.
- 3d ago First seen · 85 lines · 0 tokens per session scan A 865e8b87f0ff
frontend-dev is an agent published in the GitHub repository MakingJamie/claude-colony (12 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 512 tokens. 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
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
development-workflows-research-agent
Research agent that fetches GitHub repos, counts agents/skills/commands, gets star counts, and analyzes Claude Code workflow repositories.
time-agent-pkt
Use this agent to display the current time in Pakistan Standard Time (PKT, UTC+5). (root scope — see agent-teams for Dubai time).
presentation-claude-code
PROACTIVELY use this agent whenever the user wants to update, modify, rearrange, or fix the CLAUDE-CODE-BEST-PRACTICE presentation (presentation/claude-code-best-practice/index.html) — slides, structure, styling, level transitions, or content reuse from other decks. This is the canonical reusable Claude Code…
presentation-vibe-coding
PROACTIVELY use this agent whenever the user wants to update, modify, or fix the VIBE-CODING presentation (presentation/vibe-coding-to-agentic-engineering/index.html) — slides, structure, styling, or level transitions. Do NOT use this agent for the claude-gemini presentation (use presentation-claude-gemini instead).
documentation-analyst-writer
Use this agent when you need to analyze existing documentation and create new or updated documentation that strictly adheres to project-specific documentation standards defined in claude.md. This agent excels at maintaining consistency with established documentation patterns, ensuring technical accuracy, and producing…