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-graniangit 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-granian)<a href="https://agentmods.dev/skills/litestar-org/litestar-skills/litestar-granian"><img src="https://agentmods.dev/badge/skills/litestar-org/litestar-skills/litestar-granian/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-granian"><img src="https://agentmods.dev/badge/skills/litestar-org/litestar-skills/litestar-granian.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.00054 | $0.04091 |
| Opus 5 | $0.00027 | $0.02046 |
| Sonnet 5 | $0.00011 | $0.00818 |
| Haiku 4.5 | $0.00005 | $0.00409 |
Grade A, and why
litestar-granian 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 — 365 lines — stays where its author put it; the contents beside it link to each section on GitHub.
litestar-granian
litestar-granian 0.16.0 replaces Litestar's run command with a Granian-backed
command and integrates Granian loggers with Litestar logging. It requires
Granian 2.7.9 or later (the current lock uses 2.8.1).
Code Style Rules
- Keep handlers async when they perform I/O.
- Configure the server at the command line or programmatically via
granian.Granian. GranianPlugintakes only an optionalstaticmode keyword argument ("off"or"auto").- Use the
litestar runoption names documented here. Do not substitute similarly named options from older Granian or Uvicorn releases.
Quick Reference
Register the plugin
from litestar import Litestar, get
from litestar_granian import GranianPlugin
@get("/health")
async def health() -> dict[str, str]:
"""Return health check response."""
return {"status": "ok"}
app = Litestar(
route_handlers=[health],
plugins=[GranianPlugin()],
)
litestar --app app:app run
GranianPlugin registers the Granian-backed run command. During app
initialization, it adds missing _granian and granian.access logger entries
and a compatible formatter without replacing user-defined entries. It also
handles the standard-library logging configuration wrapped by Litestar's
StructlogPlugin.
Defaults in 0.16.0 / Granian 2.8.1
| Concern | Default |
|---|---|
| Sockets and Bind | 127.0.0.1:8000 |
| HTTP mode | auto (HTTP/1 and HTTP/2 supported; HTTP/3 not supported) |
| Workers | 1 worker (process on GIL builds; thread on free-threaded builds) |
| Runtime threads | 1 per worker |
| Runtime blocking threads | Automatically selected |
| Blocking threads | Automatically selected (30s idle timeout) |
| Runtime mode | auto (selects single- or multi-threaded Rust runtime) |
| Event loop | auto (Granian's standard selection; optional loops require their extras) |
| Async task implementation | asyncio (optional rust task scheduling) |
| Backlog | 1024 globally (minimum 128) |
| Backpressure | backlog / workers per worker (minimum 1) |
| Granian log | Enabled at info (--granian-log, --granian-log-level) |
| Access log | Disabled (--granian-access-log, --granian-access-log-fmt) |
| WebSockets | Enabled (--ws); automatically disabled in HTTP/2-only mode |
| Process supervision | Supervised process group (always) |
| Reload | Disabled (--reload; not supported on free-threaded Python) |
| Metrics | Disabled; 127.0.0.1:9090 when enabled with --metrics |
| Static-file cache | 86400 seconds; no implicit route or mount |
| Minimum TLS protocol | TLS 1.3 (--ssl-protocol-min [tls1.2|tls1.3]) |
What ships with it
3 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 · 365 lines · 54 tokens per session scan A ecb4e6354694
litestar-granian is a skill published in the GitHub repository litestar-org/litestar-skills (14 stars, last pushed 22d ago), licensed MIT. It adds 54 tokens to every session and 4,091 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).