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-reviewernpx skills add lvcoi/solidJSkills --skill solid-reviewergit clone --depth 1 https://github.com/lvcoi/solidJSkillsWrote 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/lvcoi/solidjskills/solid-reviewer)<a href="https://agentmods.dev/skills/lvcoi/solidjskills/solid-reviewer"><img src="https://agentmods.dev/badge/skills/lvcoi/solidjskills/solid-reviewer.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.00041 | $0.00544 |
| Opus 5 | $0.00020 | $0.00272 |
| Sonnet 5 | $0.00008 | $0.00109 |
| Haiku 4.5 | $0.00004 | $0.00054 |
Grade A, and why
solid-reviewer 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 5d 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-reviewer
Trigger
Use this skill for PR/diff audits where findings must be prioritized and mapped to concrete remediation.
Required Inputs
- Diff or changed files.
- Runtime context (client, SSR, SolidStart server usage if applicable).
- Known risk constraints (performance budget, accessibility requirements, release urgency).
Workflow
- Triage by severity in strict order: correctness, performance, maintainability, accessibility.
- Validate reactive boundaries first: derivations vs effects, dependency explosion, stale closures.
- Evaluate control flow and async completeness (
loading,empty,error,success). - Check SSR/hydration and browser-only assumptions in render paths.
- Ensure every finding includes file reference and concrete fix direction.
- Return validation commands relevant to touched surface.
Failure Modes
- Missing diff context: fail and request files or patch.
- Findings without reproducible impact: downgrade to question or remove.
- Suggestions without file-level anchor: invalid until anchored.
- No findings detected: explicitly state "No findings" and list residual test gaps.
Output Contract
Return output matching ReviewOutput schema at ../../skills/contracts/review-output.schema.json with:
summary,findings,open_questions,validation_commands.findingsordered by severity and containingfile(andlinewhen available).citations: every standards claim must include normalizeddoc_id+claim.
Validation
node tools/scripts/validate-skills.mjs --skill solid-reviewernode tools/scripts/validate-output-contracts.mjs
References
../../references/solidjs-normalized/manifest.jsonl../../references/solidjs-normalized/taxonomy.json../../references/solidjs/review-checklist.md../../references/solidjs/control-flow.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.
- 5d ago First seen · 63 lines · 41 tokens per session scan A 7f44c4d3b28e
solid-reviewer is a skill published in the GitHub repository lvcoi/solidJSkills (10 stars, last pushed 6mo ago), licensed MIT. It adds 41 tokens to every session and 544 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…