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 skills/lvcoi/solidjskills/solid-design-patternsnpx skills add lvcoi/solidJSkills --skill solid-design-patternsgit clone --depth 1 https://github.com/lvcoi/solidJSkillsWhat 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 | $0.00037 | $0.00491 |
| Opus 5 | $0.00018 | $0.00246 |
| Sonnet 5 | $0.00007 | $0.00098 |
| Haiku 4.5 | $0.00004 | $0.00049 |
Grade A, and why
solid-design-patterns 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
solid-design-patterns
Trigger
Use this skill for architecture decisions where multiple SolidJS patterns are viable and tradeoffs must be explicit.
Required Inputs
- Problem statement and constraints.
- Performance and SSR/hydration expectations.
- Team maintainability constraints.
- Migration constraints from current architecture.
Workflow
- Frame decision boundaries and non-negotiable constraints.
- Compare 2-3 options with explicit fit/cost profile.
- Call out anti-patterns and regression risks for each option.
- Recommend one option with phased adoption path.
- Include validation commands and measurable acceptance criteria.
Failure Modes
- Constraint ambiguity: do not recommend until constraints are explicit.
- Single-option output: invalid unless alternatives are infeasible and reason is documented.
- Recommendation without migration path: add phased plan before completion.
- No verification criteria: output fails validation.
Output Contract
Return output matching DesignDecisionOutput schema at ../../skills/contracts/design-decision-output.schema.json with:
decision_statement,constraints,options,recommended_option.tradeoffs,adoption_plan,validation_commands.citations: each architectural claim must cite normalizeddoc_idand rationale.
Validation
node tools/scripts/validate-skills.mjs --skill solid-design-patternsnode tools/scripts/validate-output-contracts.mjs
References
../../references/solidjs-normalized/manifest.jsonl../../references/solidjs-normalized/taxonomy.json../../references/solidjs/stores-context.md../../references/solidjs/async-data.md../../references/solidjs/performance-ssr.md
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.
- 2d ago First seen · 63 lines · 37 tokens per session scan A 0ec8dea81924
solid-design-patterns is a skill published in the GitHub repository lvcoi/solidJSkills (9 stars, last pushed 6mo ago), licensed MIT. It adds 37 tokens to every session and 491 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…