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 pledgeandgrow/pledge-skills --skill solidjsgit clone --depth 1 https://github.com/pledgeandgrow/pledge-skillsWrote 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/pledgeandgrow/pledge-skills/solidjs)<a href="https://agentmods.dev/skills/pledgeandgrow/pledge-skills/solidjs"><img src="https://agentmods.dev/badge/skills/pledgeandgrow/pledge-skills/solidjs.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.00127 | $0.01321 |
| Opus 5 | $0.00063 | $0.00660 |
| Sonnet 5 | $0.00025 | $0.00264 |
| Haiku 4.5 | $0.00013 | $0.00132 |
Grade A, and why
solidjs-docs 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 8d 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SolidJS Expert (1.8+)
Official Documentation: https://docs.solidjs.com/
Quick Reference
| Topic | File |
|---|---|
Reactivity: createSignal, createEffect, createMemo, derived signals, onMount, onCleanup |
core-reactivity.md |
Components: JSX, props, event handlers, class/style, classList, refs |
core-components.md |
Stores: createStore, path syntax, produce, reconcile, unwrap |
core-stores.md |
Control Flow: Show, Switch/Match, For, Index, Dynamic, ErrorBoundary, Portal |
control-flow.md |
Context: createContext, useContext, provider patterns |
context.md |
| Ecosystem: Solid Router, SolidStart, Solid Meta, deployment, guides | ecosystem.md |
Core Philosophy
Solid is a modern JavaScript framework for building responsive, high-performing user interfaces. It embraces fine-grained reactivity — updating only the parts of the DOM that need to change when data changes, rather than re-running entire components.
Key Advantages
- Performant: Fine-grained reactivity updates only what changed — no virtual DOM diffing
- Powerful: Less memory and processing power; flexibility over how and when updates happen
- Pragmatic: Freedom to choose strategies that work best for your project
- Productive: Clear and predictable API suitable for developers of all skill levels
How Solid Differs
Unlike React or other frameworks that re-run component functions on every state change:
- Components run once — A Solid component's body executes only once, when first rendered into the DOM
- Reactive system takes over — After initial render, the reactive system monitors for state changes and updates only the relevant DOM nodes
- No virtual DOM — Solid compiles JSX directly to real DOM nodes with reactive bindings
- Signals are primitives —
createSignal,createEffect,createMemoare the building blocks
Quick Start
Create a New Project
npm init solid
# or
pnpm create solid
# or
yarn create solid
# or
bun create solid
What ships with it
6 files 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.
- 8d ago First seen · 147 lines · 127 tokens per session scan A 2a5a20baede4
solidjs-docs is a skill published in the GitHub repository pledgeandgrow/pledge-skills (10 stars, last pushed 1mo ago), licensed MIT. It adds 127 tokens to every session and 1,321 once invoked, about $0.0006 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-08-31.
Other skills, from other repositories
migrate-radix-to-base
Migrates React projects and components from Radix UI to Base UI. Use when asked to migrate from radix, move to base-ui, convert radix primitives, or switch a shadcn project's base library. Handles single components ("migrate accordion") and whole projects.
compiler-orchestrator
Orchestrate the Rust compiler port end-to-end. Discovers the current frontier, fixes failing passes, ports new passes, reviews, and commits in a loop.
compiler-commit
Use when you want to verify compiler changes and commit with the correct convention. Runs tests, lint, and format, then commits with the [compiler] or [rust-compiler] prefix.
anti-ui-slop
Stop coding agents from shipping generic UI. Extend the product's design system, use UIZZE evidence only when useful, cover required states, and inspect the rendered result.
compiler-port
Port a compiler pass from TypeScript to Rust. Gathers context, plans the port, implements in a subagent with test-fix loop, then reviews.
tamagui
Universal React UI framework for web and native. Use when building cross-platform apps with Tamagui, creating styled components with styled(), configuring design tokens/themes, using Tamagui UI components, or working with animations. Triggers: "tamagui", "styled()", "$token", "XStack/YStack", "useTheme", "@tamagui/"…