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 skills add richardcarls/solid-js-best-practices --skill solid-js-best-practicesgit clone --depth 1 https://github.com/richardcarls/solid-js-best-practicesWrote 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/skills/richardcarls/solid-js-best-practices/solid-js-best-practices)<a href="https://agentmods.dev/skills/richardcarls/solid-js-best-practices/solid-js-best-practices"><img src="https://agentmods.dev/badge/skills/richardcarls/solid-js-best-practices/solid-js-best-practices/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/skills/richardcarls/solid-js-best-practices/solid-js-best-practices"><img src="https://agentmods.dev/badge/skills/richardcarls/solid-js-best-practices/solid-js-best-practices.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.00046 | $0.05706 |
| Opus 5.5 | $0.00018 | $0.02282 |
| Sonnet 5.5 | $0.00009 | $0.01141 |
| Haiku 4.5 | $0.00005 | $0.00571 |
Grade A, and why
solid-js-best-practices 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 18d 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 — 289 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Solid.js Best Practices
Comprehensive best practices for building Solid.js applications and components, optimized for AI-assisted code generation, review, and refactoring.
Version Routing
Read the project's solid-js version from its manifest and lockfile before applying code examples.
If the major is unknown, ask which major the project uses. The existing rule files are based on
Solid 1.x; version_basis records the version behind a rule, without limiting its principle to
that major. Do not copy a 1.x API example into a 2.x project without checking its current equivalent.
Solid 2.x coverage is deferred until its official release. For a pre-release 2.x project, consult
the official 1.x migration guide and documentation
for the installed release candidate; do not treat these 1.x rules as verified 2.x guidance.
Rules by Category
1. Reactivity (7 rules)
| # | Rule | Priority | Description |
|---|---|---|---|
| 1-1 | Use Signals Correctly | CRITICAL | Always call signals as functions count() not count |
| 1-2 | Use Memo for Derived Values | HIGH | Use createMemo for computed values, not createEffect |
| 1-3 | Effects for Side Effects Only | HIGH | Use createEffect only for side effects, not derivations |
| 1-7 | No Primitives in Reactive Contexts | HIGH | Don't call hooks or create reactive primitives inside effects or memos |
| 1-4 | Avoid Setting Signals in Effects | MEDIUM | Setting signals in effects can cause infinite loops |
| 1-5 | Use Untrack When Needed | MEDIUM | Use untrack() to prevent unwanted reactive subscriptions |
| 1-6 | Batch Signal Updates | LOW | Use batch() for multiple synchronous signal updates |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 18d ago Changed · -139 lines · -58 tokens per session cf9ae584a3d5
- 2mo ago First seen · 428 lines · 104 tokens per session scan A 95c1c965e68e
solid-js-best-practices is a skill published in the GitHub repository richardcarls/solid-js-best-practices (2 stars, last pushed 14d ago), licensed MIT. It adds 46 tokens to every session and 5,706 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-31.
Other skills, from other repositories
understand-diff
Use when you need to analyze git diffs or pull requests to understand what changed, affected components, and risks.
code-reviewer
Use when asked to review, check or diagnose Spring Boot code: a pull request, diff, module or file before it merges; a slow endpoint or query (N+1, unbounded reads, JPA and Hibernate performance); security, JSpecify null-safety, architecture boundaries or Boot 4 migration risks in existing code; or whether the tests…
auto-test-code
A structured process for critically reviewing and testing software code. It records review findings, test plans, commands, results, and supporting files in a project workspace.
git-pr-review
A read-only reviewer for GitHub pull requests, which are proposed code changes submitted for review. It produces an evidence-based report about whether a pull request should be merged.
review
Plan-aware graph-enhanced code review before merge. CRITICAL issues block merge. Use after fix/verify.
flutter-dart-code-review
Library-agnostic Flutter/Dart code review checklist covering widget best practices, state management patterns (BLoC, Riverpod, Provider, GetX, MobX, Signals), Dart idioms, performance, accessibility, security, and clean architecture.