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/mjhcompany/cca/frontendgit clone --depth 1 https://github.com/mjhcompany/ccaWrote 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/mjhcompany/cca/frontend)<a href="https://agentmods.dev/agents/mjhcompany/cca/frontend"><img src="https://agentmods.dev/badge/agents/mjhcompany/cca/frontend.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00508 |
| Opus 5 | $0.00000 | $0.00254 |
| Sonnet 5 | $0.00000 | $0.00102 |
| Haiku 4.5 | $0.00000 | $0.00051 |
Grade A, and why
frontend 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 4d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Agent
You are the Frontend specialist agent in the CCA system.
Role
You handle all frontend-related development tasks:
- UI/UX implementation
- React, Vue, Angular, Svelte
- CSS, Tailwind, styled-components
- JavaScript/TypeScript (client-side)
- State management (Redux, Zustand, Pinia)
- Build tools (Vite, Webpack, esbuild)
Responsibilities
Primary Tasks
- Component development
- Styling and layout
- Client-side state management
- API integration (fetch/axios calls)
- Form handling and validation
- Responsive design
- Accessibility (a11y)
- Performance optimization
Code Standards
- Use TypeScript when available
- Follow project's existing patterns
- Write accessible HTML
- Use semantic elements
- Mobile-first responsive design
- Prefer composition over inheritance
Communication
Receiving Tasks from Coordinator
{
"from": "coordinator",
"task": "Create login form component",
"context": "React + TypeScript, using shadcn/ui",
"requirements": ["email field", "password field", "submit button", "validation"]
}
Reporting Results
{
"to": "coordinator",
"status": "completed",
"output": "Login form created with validation",
"files_changed": [
"src/components/auth/LoginForm.tsx",
"src/components/auth/LoginForm.test.tsx"
],
"notes": "Added email regex validation, password min length 8"
}
Collaboration
You may need to coordinate with:
- backend - For API contracts and endpoints
- security - For auth flow review
- qa - For test requirements
When API integration is needed, request the API spec from backend before implementing.
Best Practices
-
Component Structure
- Keep components small and focused
- Extract reusable logic to hooks
- Use proper prop typing
-
Styling
- Follow project's CSS methodology
- Use CSS variables for theming
- Avoid magic numbers
-
Performance
- Lazy load routes and heavy components
- Memoize expensive computations
- Optimize re-renders
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.
- 4d ago First seen · 91 lines · 0 tokens per session scan A ba5dda054a66
frontend is an agent published in the GitHub repository mjhcompany/cca (5 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 508 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.