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 litestar-org/litestar-skills --skill litestar-inertiagit clone --depth 1 https://github.com/litestar-org/litestar-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/litestar-org/litestar-skills/litestar-inertia)<a href="https://agentmods.dev/skills/litestar-org/litestar-skills/litestar-inertia"><img src="https://agentmods.dev/badge/skills/litestar-org/litestar-skills/litestar-inertia/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/litestar-org/litestar-skills/litestar-inertia"><img src="https://agentmods.dev/badge/skills/litestar-org/litestar-skills/litestar-inertia.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00056 | $0.04062 |
| Opus 5 | $0.00028 | $0.02031 |
| Sonnet 5 | $0.00011 | $0.00812 |
| Haiku 4.5 | $0.00006 | $0.00406 |
Grade A, and why
litestar-inertia 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 12d 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 — 430 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Litestar + Inertia.js Integration
litestar-inertia is the four-library story:
| Layer | Library | Role |
|---|---|---|
| Client SPA | @inertiajs/react / @inertiajs/vue3 / @inertiajs/svelte |
Page resolution, forms, navigation, shared data access; generated templates target Inertia v3 |
| Frontend build | vite |
Bundling, HMR, dev server, production build |
| Python bridge | litestar-vite |
VitePlugin + InertiaConfig, asset manifest, type generation, page-props codec |
| Server framework | litestar |
Routes, Controllers, Guards, DI, DTOs — returning Inertia responses |
Litestar routes produce page data, ViteConfig.inertia configures the response
layer, and the Vite-served client handles subsequent navigations. For Vite-only
configuration, use the sibling skill.
When this skill activates
- Python files importing
litestar_vite.inertia,InertiaConfig, or route handlers withcomponent= *.tsx/*.vue/*.sveltefiles importing from@inertiajs/*createInertiaApp({ resolve, setup })in a frontend entrypoint- A
resources/orresources/js/pages/directory alongside asrc/py/— classic litestar-vite + Inertia layout inertia.config.tsor anInertiaConfiginvocation invite.config.ts- User asks about "building an SPA with a Python backend", "server-driven React/Vue", "form validation errors from Python", "shared auth data across pages"
Code Style Rules
- PEP 604 unions in consumer Python modules; use
from __future__ import annotationsonly when the application benefits from it - TypeScript typed pages — generate page-props types via
litestar-vite's TypeGen, never hand-roll - Forms via
useForm— use the adapter form helper for errors, submission state, and navigation - CSRF via Litestar state — configure Litestar
CSRFConfigand wirecsrfHeaders()into global Inertia visit options; generated scaffolds already do this, including withcookie_httponly=True - Shared data for auth + flash, never page-specific. Static page props go in
InertiaConfig.extra_static_page_props; session-backed props go inextra_session_page_props; request-time flashes useshare(request, ...). - camelCase on the wire — define msgspec structs with
class Example(msgspec.Struct, rename="camel"); generated TypeScript consumes the serialized names - Partial reloads over full-page reloads when only a subset of props changes (
router.reload({ only: ['notifications'] })) - Lazy props for expensive-to-compute page data the user may not need on first paint
What ships with it
2 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.
- 12d ago First seen · 430 lines · 56 tokens per session scan A c9c3847adaae
litestar-inertia is a skill published in the GitHub repository litestar-org/litestar-skills (14 stars, last pushed 23d ago), licensed MIT. It adds 56 tokens to every session and 4,062 once invoked, about $0.0003 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-30.
Other skills, from other repositories
create-site
Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…
liveview-patterns
Build LiveView: async data (assignasync), PubSub (check connected?), phx-change events, form components/modals/uploads, streams for lists, livepatch. Use when handling interactions, debugging events, or tracking Presence.
cesiumjs-core-utilities
CesiumJS core utilities and networking - Resource, Color, Event, Request, RequestScheduler, error handling, helper functions, feature detection. Use when fetching remote data, managing HTTP requests, working with colors, handling events, debugging errors, or using utility functions like defined, clone, or…
fec-data-fetching
A frontend guide for handling data that comes from a server, including typed requests, caching, refreshing, pagination, and updates. Server state means data owned by an API rather than by a page’s local controls.
fec-react-project-standard
A guide for organizing medium-sized or large React and TypeScript projects. It defines boundaries between pages, business features, shared components, hooks, services, state, APIs, and utilities.
fec-vue3-project-standard
A Vue 3 and TypeScript project standard covering component boundaries, composables, routing, Pinia state, API layers, errors, styles, and project structure. Vue is a frontend framework, and composables are reusable functions for sharing component logic.