agentmods.dev

solid-start-server-runtime

A guide to server-side code in SolidStart, a framework for building web applications with SolidJS. It covers request handlers, middleware, server functions, and request events while keeping client and server code separate.

In plain words
What is it for?
Use it to design SolidStart APIs, protected routes, middleware, server functions, and request or response behavior.
Why use it?
It helps resolve unclear boundaries and runtime assumptions before implementing an API. It also requires decisions about deployment, authentication, responses, errors, and headers.

Skill for Claude CodeCodex

9 6mo ago A scan 38 tokens original MIT
View the source file lvcoi/solidJSkills
Install

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.

agentmods
npx agentmods add skills/lvcoi/solidjskills/solid-start-server-runtime
Any agent
npx skills add lvcoi/solidJSkills --skill solid-start-server-runtime
Clone the repo
git clone --depth 1 https://github.com/lvcoi/solidJSkills

Made for: Claude Code, Codex.

Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 547 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00038 $0.00547
Opus 5 $0.00019 $0.00273
Sonnet 5 $0.00008 $0.00109
Haiku 4.5 $0.00004 $0.00055

Measured 2d ago against content hash 882dfd05c995, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

solid-start-server-runtime 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.

skills/solid-start-server-runtime/SKILL.md · 66 lines

How it starts

The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.

solid-start-server-runtime

Trigger

Use for SolidStart server runtime concerns: handlers, middleware, server functions, request event usage, and response behavior.

Required Inputs

  • Server runtime target and deployment constraints.
  • Route/API behavior and auth/session requirements.
  • Error/status/header handling expectations.

Workflow

  1. Map endpoint responsibilities to SolidStart server primitives.
  2. Select middleware boundaries and request event usage.
  3. Define response/status/header semantics and failure handling.
  4. Produce handoff notes for implementation and security checks.

Failure Modes

  • Runtime/deployment target unspecified: request target before decisions.
  • Mixed client/server concerns without boundaries: enforce boundary split.
  • Missing auth/session model for protected endpoints: block completion.

Output Contract

Return DomainGuidanceOutput with runtime decisions, handoff steps, validation commands, and citations including doc_id.

Validation

  • node tools/scripts/validate-skills.mjs --skill solid-start-server-runtime
  • node tools/scripts/validate-solid-corpus.mjs

Key Corpus References

Use these doc_id values with the read_corpus_doc MCP tool:

  • solid-start.solid-start.reference.server.use-server — server function declarations
  • solid-start.solid-start.reference.server.create-middleware — middleware composition
  • solid-start.solid-start.reference.server.create-handler — custom server handlers
  • solid-start.solid-start.advanced.request-events — request event lifecycle
  • solid-start.solid-start.advanced.middleware — middleware patterns and ordering

References

  • ../../references/solidjs-normalized/docs/solid-start/reference/server/create-handler.md
  • ../../references/solidjs-normalized/docs/solid-start/reference/server/create-middleware.md
  • ../../references/solidjs-normalized/docs/solid-start/reference/server/use-server.md
  • ../../references/solidjs-normalized/docs/solid-start/advanced/request-events.md
  • ../../references/solidjs-normalized/manifest.jsonl

Read the full file on GitHub · 66 lines

Files

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.

Changes

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.

  1. 2d ago First seen · 66 lines · 38 tokens per session scan A 882dfd05c995

Subscribe to this mod's changes

solid-start-server-runtime is a skill published in the GitHub repository lvcoi/solidJSkills (9 stars, last pushed 6mo ago), licensed MIT. It adds 38 tokens to every session and 547 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.

Backend and APIs
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens