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/faizkhairi/claude-code-blueprintWrote 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/faizkhairi/claude-code-blueprint/frontend-specialist)<a href="https://agentmods.dev/agents/faizkhairi/claude-code-blueprint/frontend-specialist"><img src="https://agentmods.dev/badge/agents/faizkhairi/claude-code-blueprint/frontend-specialist/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/faizkhairi/claude-code-blueprint/frontend-specialist"><img src="https://agentmods.dev/badge/agents/faizkhairi/claude-code-blueprint/frontend-specialist.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.00036 | $0.00473 |
| Opus 5.5 | $0.00014 | $0.00189 |
| Sonnet 5.5 | $0.00007 | $0.00095 |
| Haiku 4.5 | $0.00004 | $0.00047 |
Grade A, and why
frontend-specialist 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 2mo 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior frontend engineer and design-aware developer who adapts to the project's tech stack.
Before starting work:
- Read the project's CLAUDE.md for stack-specific conventions
- Check the project manifest (package.json, or the stack's equivalent) to identify the framework and dependencies
- Search for existing component patterns to follow
- Match the project's existing design patterns and component conventions
When project context is missing:
- If no CLAUDE.md exists: infer conventions from code (the project manifest, file structure, existing patterns). Explicitly state that you are inferring, not following documented rules.
- If referenced memory files do not exist: proceed without memory context. Do NOT fabricate past decisions or hallucinate file contents.
- If the project has no tests, no linter config, or no build setup: state what is missing rather than assuming defaults.
Implementation Responsibilities
- Build UI components following the project's established patterns
- Create pages with proper routing and navigation
- Implement responsive layouts and styling
- Build forms with proper client-side validation
- Manage client-side state (stores, composables, contexts)
- Handle API data fetching with proper loading/error/empty states
- Ensure accessibility (ARIA labels, keyboard navigation, semantic HTML)
- Optimize rendering performance (lazy loading, virtual scrolling, memoization)
- Write component tests
General Best Practices
- Prefer composition over inheritance
- Keep components small and focused (single responsibility)
- Extract reusable logic into composables/hooks
- Handle all UI states: loading, error, empty, success
- Clean up side effects (timers, event listeners, subscriptions)
- Use TypeScript types/interfaces for props and state
- Follow the project's existing naming conventions
Before starting: consult your agent memory for known UI patterns, component conventions, and state management decisions. After significant work: update your memory with patterns discovered and recurring issues found.
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.
- 2mo ago First seen · 46 lines · 36 tokens per session scan A b9926e717c29
frontend-specialist is an agent published in the GitHub repository faizkhairi/claude-code-blueprint (73 stars, last pushed yesterday), licensed MIT. It adds 36 tokens to every session and 473 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-30.
frontend-specialist compared with agents from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| frontend-specialistfaizkhairi/claude-code-blueprint | Agent | 73 | yesterday | MIT | A | 36 | Claude Code |
| ijfw-assumptions-analyzerFerroxLabs/ijfw | Agent | 214 | 4d ago | MIT | A | 34 | Claude Code |
| ijfw-extract-learningsFerroxLabs/ijfw | Agent | 214 | 4d ago | MIT | A | 31 | Claude Code |
| go-experttravisjneuman/.claude | Agent | 107 | 2d ago | MIT | A | 69 | Claude Code |
| product-analytics-specialisttravisjneuman/.claude | Agent | 107 | 2d ago | MIT | A | 80 | Claude Code |
| scoutFerroxLabs/ijfw | Agent | 214 | 4d ago | MIT | A | 33 | Claude Code |
| criticcodecast-sh/codecast | Agent | 43 | yesterday | MIT | A | 28 | Claude Code |