Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/litestar-org/litestar-skillsnpx agentmods add skills/litestar-org/litestar-skills/litestar-styleguideWrote 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-styleguide)<a href="https://agentmods.dev/skills/litestar-org/litestar-skills/litestar-styleguide"><img src="https://agentmods.dev/badge/skills/litestar-org/litestar-skills/litestar-styleguide/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-styleguide"><img src="https://agentmods.dev/badge/skills/litestar-org/litestar-skills/litestar-styleguide.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Rogue Agent · line 31 Skill modifies its own code, configuration, or behavior at runtime. Self-modification enables an agent to escalate privileges, disable safety constraints, or install persistent backdoors.Fix: Prevent the skill from modifying its own code, SKILL.md, or configuration files. Treat skill files as read-only at runtime.
- medium Agent Snooping · line 25 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 26 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 27 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00054 | $0.01988 |
| Opus 5.5 | $0.00022 | $0.00795 |
| Sonnet 5.5 | $0.00011 | $0.00398 |
| Haiku 4.5 | $0.00005 | $0.00199 |
Grade A, and why
litestar-styleguide 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 8d 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
litestar-styleguide
This is the shared style baseline that every other skill in this plugin references. It exists so that cross-cutting rules (PEP 604 unions, async I/O, ruff + mypy + pyright + prek, test file naming, CI/CD conventions) live in exactly one place — and individual skills stay focused on their framework or tool-specific surface.
Code Style Rules
- Terse, imperative, authoritative. State the preferred choice and a one-line
Reason:; never hedge ("you might want to…"). - PEP 604 unions (
T | None) and PEP 585 generics (list[T],dict[K, V]). Never usetyping.Optional,typing.Union,typing.List, ortyping.Dict. from __future__ import annotationsis a library-author guardrail, not a consumer rule. Application code (handlers, services, tests) MAY use it; avoid it only in modules defining runtime-introspected types (msgspec.Struct, SQLAlchemyMapped[...], Dishka@provide, SAQ@task).- Keep runtime-inspected route annotations at module top-level (
# noqa: TC001, TC002). Whenfrom __future__ import annotationsand Ruffflake8-type-checking(TC) are active in Litestar controller/handler modules, keepRequest,NamedDependency,FromDishka,FromPath,FromQuery,JSONBody, and request/response DTO imports at module top-level with# noqa: TC001, TC002(or"**/controllers.py" = ["TC001", "TC002", "TC003"]inper-file-ignores), never insideif TYPE_CHECKING:. Reason: Litestar and Dishka inspect handler annotations at runtime during app startup and OpenAPI generation. - Async all I/O, Google-style docstrings, function-based pytest tests (
@pytest.mark.anyio). - Litestar first-party stack bias with match-your-stack flexibility. Prefer
msgspec,advanced-alchemy/sqlspec,litestar-granian,litestar-saq/litestar-queueswhen starting fresh, and match the user's existing stack when present.
Quick Reference
| Slice | Reference File | Key Topics |
|---|---|---|
| Cross-language principles | references/general.md |
Simplicity over cleverness, boundary validation, naming, import order |
| Python conventions | references/python.md |
PEP 604/585, # noqa: TC001, TC002, msgspec.Struct, async I/O, docstrings, ruff, mypy, pyright, prek |
| Litestar baseline | references/litestar.md |
Typed markers (FromPath, FromQuery, JSONBody, RequestBody, NamedDependency, SkipValidation), Provide vs Dishka, MsgspecDTO, Guards, plugins |
| TypeScript conventions | references/typescript.md |
Strict tsconfig, discriminated unions, named exports, oxlint / biome |
| Testing conventions | references/testing.md |
pytest + anyio, AsyncTestClient lifespan fixtures, Vitest, 90%+ coverage |
| CI/CD conventions | references/ci-cd.md |
GitHub Actions with setup-uv, prek / .pre-commit-config.yaml, matrix builds |
| Canonical reference apps | references/canonical-apps.md |
litestar-fullstack-inertia, litestar-fullstack, litestar-sqlstack, oracledb-vertexai-demo |
| Google Developer Knowledge MCP | references/google-developer-knowledge-mcp.md |
Opt-in MCP setup for fresh GCP / Firebase / Maps documentation |
What ships with it
8 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.
- 8d ago Changed · +1 lines bd8f6a284932
- 1mo ago Changed · +26 lines 59ca5af446c7
- 1mo ago First seen · 103 lines · 54 tokens per session scan A f6aa3284aca3
litestar-styleguide is a skill published in the GitHub repository litestar-org/litestar-skills (16 stars, last pushed yesterday), licensed MIT. It adds 54 tokens to every session and 1,988 once invoked, about $0.0002 per session on Opus 5.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/.
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…
functions-development
Build serverless Go or Python functions for Falcon Foundry apps. TRIGGER when user asks to "create a function", "write a serverless function", "build backend logic", runs foundry functions create, or needs help with FDK handler patterns, function testing, or collection integration from functions. Also TRIGGER when…
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).