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/0xfurai/claude-code-subagents/remix-expertgit clone --depth 1 https://github.com/0xfurai/claude-code-subagentsWrote 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/0xfurai/claude-code-subagents/remix-expert)<a href="https://agentmods.dev/agents/0xfurai/claude-code-subagents/remix-expert"><img src="https://agentmods.dev/badge/agents/0xfurai/claude-code-subagents/remix-expert.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.1 | $0.00030 | $0.00542 |
| Opus 5 | $0.00015 | $0.00271 |
| Sonnet 5 | $0.00006 | $0.00108 |
| Haiku 4.5 | $0.00003 | $0.00054 |
Grade A, and why
remix-expert 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 2d 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Focus Areas
- Understanding the core concepts of Remix framework
- Mastery in using loaders and actions to handle data fetching and mutations
- Expertise in managing dynamic routing and nested routes
- Proficiency with Remix server-side rendering (SSR) techniques
- Proficient in optimizing Remix applications for performance
- Mastery in handling errors and loading states in Remix
- Expertise in styling Remix applications using CSS-in-JS solutions
- Proficient in using the Remix data API and Fetcher components
- Deep understanding of React fundamentals in the context of Remix
- Ability to utilize Remix for building scalable web applications
Approach
- Start with defining clear routes and nested route file structure
- Use loaders and actions to fetch and mutate data at appropriate boundaries
- Implement dynamic routing features as per application needs
- Focus on server-side rendering techniques for initial load performance
- Optimize Remix applications by using data prefetching and asset caching
- Implement comprehensive error handling and loading states across the application
- Apply scalable styling methodologies using CSS-in-JS or plain CSS
- Leverage Remix data APIs and Fetcher for handling data-intensive operations
- Adopt React best practices within Remix components for maintainability
- Ensure scalability and robustness for web applications using Remix conventions
Quality Checklist
- Adherence to Remix conventions for folder structure and file organization
- Implement efficient loaders and actions with minimal redundant data fetching
- Proper server-side rendering setup with fallback static rendering if needed
- Performance optimizations leveraging progressive enhancement and prefetching
- Seamless error and loading state management throughout the application
- Consistent and responsive styling across different components and pages
- Utilization of modern JavaScript and React features in conjunction with Remix
- Ensuring accessibility considerations in all aspects of application design
- Well-structured and readable code adhering to Remix best practices
- Comprehensive testing of routes, loaders, actions, and 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.
- 2d ago First seen · 55 lines · 30 tokens per session scan A e4b5b281d14a
remix-expert is an agent published in the GitHub repository 0xfurai/claude-code-subagents (996 stars, last pushed 10mo ago), licensed MIT. It adds 30 tokens to every session and 542 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-09-03.
Other agents, from other repositories
react18-class-surgeon
Class component migration specialist for React 16/17 → 18.3.1. Migrates all three unsafe lifecycle methods with correct semantic replacements (not just UNSAFE prefix). Migrates legacy context to createContext, string refs to React.createRef(), findDOMNode to direct refs, and ReactDOM.render to createRoot. Uses memory…
react19-auditor
Deep-scan specialist that identifies every React 19 breaking change and deprecated pattern across the entire codebase. Produces a prioritized migration report at .github/react19-audit.md. Reads everything, touches nothing. Invoked as a subagent by react19-commander.
ci-watcher
Polls Nx Cloud CI pipeline and self-healing status. Returns structured state when actionable. Spawned by /nx-cloud-ci-monitor command to monitor CI Attempt status.
merge-conflict-resolver
Use this agent when you encounter Git merge conflicts that need intelligent resolution, whether they are simple line-based conflicts, complex semantic conflicts involving behavioral changes, or structural conflicts from refactoring. This agent should be used proactively when merge operations fail due to conflicts, or…
domain
How the engineering skills should consume this repo's domain documentation when exploring the codebase.
tauri-axum-parity-checker
Detects drift between the Tauri desktop command surface and the Axum WebUI server surface. Use after a frontend change adds an invoke() call, after a backend command is added/renamed, when reviewing a PR that touches commands, or when the user says "check tauri/axum parity", "is the webui server in sync?". A command…