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 litestargit 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)<a href="https://agentmods.dev/skills/litestar-org/litestar-skills/litestar"><img src="https://agentmods.dev/badge/skills/litestar-org/litestar-skills/litestar/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"><img src="https://agentmods.dev/badge/skills/litestar-org/litestar-skills/litestar.svg" alt="Reviewed on agentmods" width="80" 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.00057 | $0.01113 |
| Opus 5 | $0.00028 | $0.00557 |
| Sonnet 5 | $0.00011 | $0.00223 |
| Haiku 4.5 | $0.00006 | $0.00111 |
Grade A, and why
litestar 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 11d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Litestar Routing Hub
Use this skill to choose the right focused Litestar skill and keep app-level choices coherent. For implementation details, open the narrow skill that matches the task.
This guidance targets the released Litestar 2.24.0 contract. Do not copy
unreleased main APIs into consumer examples.
Code Style Rules
- Prefer first-party Litestar ecosystem packages and patterns.
- Match the project's existing stack for data access, serialization, DI, settings, background jobs, and deployment.
- Keep app setup thin: compose routes, plugins, dependencies, middleware, exception handlers, and settings from domain modules.
- Use async I/O for request handlers, service methods, background integration, and external clients.
Quick Reference
| Task | Skill |
|---|---|
| Controllers, route decorators, Routers, domain folders | litestar-routing |
| DTOs, request bodies, response schemas, OpenAPI | litestar-dto-openapi |
| Authentication, authorization, Guards | litestar-auth-guards |
| Provide, dependency maps, Dishka wiring | litestar-di |
| Repositories, services, filters, pagination | litestar-data-services |
| Settings, env loading, app state | litestar-settings |
| Domain exceptions and exception handlers | litestar-exceptions |
| Built-in or custom middleware | litestar-middleware |
| Plugin protocols and app plugin composition | litestar-plugins |
| WebSockets, SSE, Channels | litestar-realtime |
| Google ADK / agent HTTP serving | litestar-ai-serving |
| Tests | litestar-testing |
| Build artifacts | litestar-build |
| Deployment targets | litestar-deployment |
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.
- 11d ago First seen · 101 lines · 57 tokens per session scan A b31f094bfb69
litestar is a skill published in the GitHub repository litestar-org/litestar-skills (14 stars, last pushed 21d ago), licensed MIT. It adds 57 tokens to every session and 1,113 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
python-backend-expert
This skill should be used when the user is writing, reviewing, debugging, or architecting Python backend code using Litestar or FastAPI with SQLAlchemy or Advanced Alchemy. Provides expert critique covering SOLID principles, hexagonal architecture, repository/service patterns, dependency injection, async correctness…
odoo-python
Use when writing or reviewing any Python in an Odoo module — models, computes, overrides, controllers, wizards. Carries PSAE review-derived principles for ORM correctness, performance, style, and security, plus references for exact patterns. Invoke before writing logic in models/, controllers/, or wizard/.
fastapi
FastAPI best practices and conventions. Use when working with FastAPI APIs and Pydantic models for them. Keeps FastAPI code clean and up to date with the latest features and patterns, updated with new versions. Write new code or refactor and update old code.
cloudflare-workers-multi-lang
Multi-language Workers development with Rust, Python, and WebAssembly. Use when building Workers in languages other than JavaScript/TypeScript, or when integrating WASM modules for performance-critical code.
craftcms
Craft CMS 5 plugin and module development — extending Craft with PHP. Covers elements, element queries, services, models, records, controllers, migrations, queue jobs, console commands, field types, native fields, events, behaviors, Twig extensions, widgets, filesystems, permissions, project config, GraphQL, testing…
python-services
Python patterns for CLI tools, async parallelism, and backend services. Use when building CLI apps, async/parallel Python, FastAPI services, background jobs, or configuring Python project tooling (uv, ruff, ty).