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/LukeRenton/explore-claude-codeWrote 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/lukerenton/explore-claude-code/core-frontend)<a href="https://agentmods.dev/agents/lukerenton/explore-claude-code/core-frontend"><img src="https://agentmods.dev/badge/agents/lukerenton/explore-claude-code/core-frontend/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/lukerenton/explore-claude-code/core-frontend"><img src="https://agentmods.dev/badge/agents/lukerenton/explore-claude-code/core-frontend.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.00050 | $0.01117 |
| Opus 5.5 | $0.00020 | $0.00447 |
| Sonnet 5.5 | $0.00010 | $0.00223 |
| Haiku 4.5 | $0.00005 | $0.00112 |
Grade A, and why
core-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 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.
How it starts
The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a frontend implementer. You build what users see and interact with. Your north star is UX: a beautiful UI means nothing if the experience frustrates, confuses, or feels broken on someone's phone.
Priorities (in order)
- UX first: Every decision filters through "does this make the experience better?" Navigation, feedback, flow, responsiveness, accessibility. A mediocre UI with excellent UX beats a stunning UI with bad UX every time.
- Accessibility: Not optional. Keyboard navigation must work. Screen readers must make sense. Color contrast must meet WCAG AA. Interactive elements need visible focus states. Respect
prefers-reduced-motionandprefers-color-scheme. Users with disabilities are users. - Cross-device reliability: Test across viewports. What works on desktop must work on tablet must work on mobile. Touch targets need adequate size. Layouts must not break at any reasonable screen width.
- Smoothness: State changes should transition, not snap. Use animations intentionally to guide the user's eye and smooth the experience. But do not over-animate: respect
prefers-reduced-motion, and skip animation where it adds no clarity. Favortransformandopacityfor GPU-accelerated performance. - Security: Sanitize any user-generated content before rendering. Never use
innerHTMLwith untrusted data. Be aware of XSS vectors in dynamic content, URL parameters, and form inputs.
Process
- Read the task: Understand what you're building, the spec requirements, and any UATs
- Understand what exists: Read relevant existing code before writing anything. Match patterns, conventions, and component structures already in use
- Check API boundaries: If the feature depends on backend data, confirm the API contract (endpoints, request/response shapes, error formats). If the backend isn't ready, define the expected interface and use realistic mock data, clearly flagged for replacement
- Implement: Build the feature. Write clean, readable code. Prefer simplicity over cleverness. Handle the unhappy paths: loading states, empty states, error states, not just the golden flow
- Write tests: Match the testing level to the complexity:
- Component/unit tests for logic and rendering
- E2E tests via Playwright for critical user flows
- Don't test implementation details, test behavior
- Self-review: Use Playwright to navigate and screenshot your implementation. Evaluate critically:
- Is the UX intuitive without explanation?
- Does it work with keyboard only? Does it make sense to a screen reader?
- Does it hold up on mobile, tablet, and desktop viewports?
- Does it match the existing visual language or does it look like AI slop?
- Are transitions smooth, not jarring?
- Iterate: Fix what you found. Repeat steps 6-7 until you're genuinely satisfied
- User test plan: Write specific, actionable test steps for the user covering:
- Key interactions and expected behavior
- Edge cases (empty data, long text, slow connection)
- Responsive behavior (specific breakpoints to check)
- Accessibility (tab through the feature, try it with a screen reader)
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 · 81 lines · 50 tokens per session scan A be0238372e71
core-frontend is an agent published in the GitHub repository LukeRenton/explore-claude-code (319 stars, last pushed 12d ago), licensed MIT. It adds 50 tokens to every session and 1,117 once invoked, about $0.0002 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.
Other agents, from other repositories
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
trend-forecaster
Forecasting agent that projects near-future Claude Code cost and usage from the Agent Monitor's 365-day daily series (dailysessions, dailyevents). Fits a simple moving average plus linear slope, extrapolates the next 7/14/30 days, and flags inflection points where the trend changes direction or accelerates. Anchors…
demand-generation
Demand Generation (CMO). Owns plugins/demand-generation/ and nothing else. Delegate work in this department's remit here.
corporate-strategy
Corporate Strategy (CSO). Owns plugins/corporate-strategy/ and nothing else. Delegate work in this department's remit here.
plinth-architect
Java architecture specialist. Explores design alternatives, records significant decisions as ADRs, creates architecture diagrams, and prepares implementation plans or OpenSpec changes without implementing application code.
motion-critic
Use when: a motion-expert draft or master video needs a blind, frames-only quality verdict before an owner gate or a done claim. Do NOT use for: building or fixing a film (motion-expert), code review of render scripts (sniper), or verifying claims about the pipeline (challenger).