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/solidjs-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/solidjs-expert)<a href="https://agentmods.dev/agents/0xfurai/claude-code-subagents/solidjs-expert"><img src="https://agentmods.dev/badge/agents/0xfurai/claude-code-subagents/solidjs-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.00020 | $0.00361 |
| Opus 5 | $0.00010 | $0.00180 |
| Sonnet 5 | $0.00004 | $0.00072 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
solidjs-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.
What it actually says
Focus Areas
- Understanding SolidJS reactivity system
- Building reusable components
- Optimizing rendering performance
- Managing state with stores and signals
- Handling side effects with createEffect
- Composing UI with nested components
- Leveraging context API for global state
- Integrating custom hooks for shared logic
- Implementing router for navigation
- Testing SolidJS components
Approach
- Emphasize fine-grained reactivity over VDOM
- Use signals for state management efficiently
- Decompose UI into atomic components
- Frequently profile and optimize slow paths
- Minimize unnecessary computations and renders
- Apply consistent naming conventions
- Adhere to best practices from SolidJS docs
- Prefer built-in hooks before creating custom
- Refactor to remove duplication and complexity
- Document components with clear examples
Quality Checklist
- Components are functionally reusable
- Signals and stores are used appropriately
- Declarative over imperative coding style
- CSS encapsulation in components
- Well-defined props with default values
- Input validation with relevant feedback
- Minimal business logic in the components
- Consistent coding style across components
- Comprehensive and meaningful tests
- Profiled and benchmarked performance
Output
- SolidJS components with clear API
- Readable and maintainable codebase
- Comprehensive test suite for components
- Performance benchmarking reports
- Documentation with usage examples
- Refactored code for improved clarity
- Type-safe implementations with TS support
- Optimized critical rendering paths
- Minimal and understandable JSX
- Harmonic and responsive UI layouts
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 · 57 lines · 20 tokens per session scan A bae64e2251e6
solidjs-expert is an agent published in the GitHub repository 0xfurai/claude-code-subagents (996 stars, last pushed 10mo ago), licensed MIT. It adds 20 tokens to every session and 361 once invoked, about $0.0001 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
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.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
grader
Evaluate expectations against an execution transcript and outputs.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.