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-data-servicesgit 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-data-services)<a href="https://agentmods.dev/skills/litestar-org/litestar-skills/litestar-data-services"><img src="https://agentmods.dev/badge/skills/litestar-org/litestar-skills/litestar-data-services/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-data-services"><img src="https://agentmods.dev/badge/skills/litestar-org/litestar-skills/litestar-data-services.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.00042 | $0.00489 |
| Opus 5 | $0.00021 | $0.00244 |
| Sonnet 5 | $0.00008 | $0.00098 |
| Haiku 4.5 | $0.00004 | $0.00049 |
Grade A, and why
litestar-data-services 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Litestar Data Services
Use this skill for repositories, service layers, CRUD boundaries, filters, and pagination.
Code Style Rules
- Match the existing persistence stack before choosing patterns.
- Keep handlers out of query construction and transaction management.
- Use filter dependency objects rather than ad hoc query params.
- Return typed pagination envelopes for collection endpoints.
Quick Reference
- Service patterns: services.md
- Pagination and filters: pagination.md
- Advanced Alchemy details: advanced-alchemy
- sqlspec details: sqlspec
Workflow
- Identify the project's data stack.
- Put persistence operations behind a service boundary.
- Add filters and pagination through the stack's native pattern.
- Return DTO-ready data to Controllers.
Guardrails
- Do not mix repository stacks in one feature.
- Do not place SQL or ORM session handling in route handlers.
- Do not hand-roll pagination query params.
- Do not return persistence internals when DTOs are required.
Validation Checkpoint
- Service methods own data access.
- Filters and pagination match the selected stack.
- Controller code stays thin.
- DTO conversion is explicit or handled by the service stack.
Example
class UserService(SQLAlchemyAsyncRepositoryService[User]):
repository_type = UserRepository
References Index
Official References
- https://docs.litestar.dev/ - Litestar documentation
- https://docs.litestar.dev/latest/reference/ - Litestar API reference
Shared Styleguide Baseline
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 · 83 lines · 42 tokens per session scan A acadba7e49be
litestar-data-services is a skill published in the GitHub repository litestar-org/litestar-skills (14 stars, last pushed 22d ago), licensed MIT. It adds 42 tokens to every session and 489 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-30.
Other skills, from other repositories
phoenix-contexts
Phoenix context design — creating/splitting contexts, Scope (1.8+), Ecto.Multi, PubSub, routers, plugs, controllers. Use when editing contexts, routers, or designing boundaries.
motherduck-rest-api
Administer MotherDuck service accounts, tokens, Ducklings, and Dive embed sessions through the control-plane REST API.
motherduck-connect
Set up or troubleshoot MotherDuck connections, authentication, client runtimes, and read scaling.
craft-model
Crafting the Eloquent model. Source of truth.
craft-query
Crafting QueryBuilders. Eloquent power, not Repositories.
domain-modeling
Use when introducing, reviewing, or renaming a top-level type, table, or domain concept; or choosing where state lives (in-memory vs persistent).