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 llodev/skills --skill ts-query-cqrsgit clone --depth 1 https://github.com/llodev/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/llodev/skills/ts-query-cqrs)<a href="https://agentmods.dev/skills/llodev/skills/ts-query-cqrs"><img src="https://agentmods.dev/badge/skills/llodev/skills/ts-query-cqrs/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/llodev/skills/ts-query-cqrs"><img src="https://agentmods.dev/badge/skills/llodev/skills/ts-query-cqrs.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.00080 | $0.00900 |
| Opus 5.5 | $0.00032 | $0.00360 |
| Sonnet 5.5 | $0.00016 | $0.00180 |
| Haiku 4.5 | $0.00008 | $0.00090 |
Grade A, and why
ts-query-cqrs 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 2mo 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TypeScript DDD Query (CQRS Read Side)
MANDATORY — READ ENTIRE FILE: Before any implementation step, read
references/query-cqrs-pattern.md completely.
Then load the adapter reference for your infrastructure:
- Prisma → also read
references/prisma-adapter.mdcompletely. - Other adapters (Firestore, MongoDB, Supabase…) → reference files not yet available; apply the principles from
query-cqrs-pattern.md.
Do NOT load other DDD skills (entity, use-case, repository) unless explicitly requested.
Before You Start
Before defining a single interface, answer:
- Read or write? If the caller needs the entity to run domain logic →
Repository. If the caller only needs data to display →Query. When in doubt, check the table below. - Projection shape? What does the consumer actually need? Individual fields only — never return the full entity from a query.
- Pagination? Does the list need
page/pageSize? UsePaginatedResultDTO<XxxListItem>. - Filters? Map optional filters to conditional
WHEREclauses in the adapter — never hard-code them.
Query vs Repository Decision Table
| Situation | Use | Why |
|---|---|---|
| Display a list on the front-end | Query |
Returns DTO, no entity overhead |
| Load entity before an update/delete | Repository.findById |
Needs domain invariants (cloneWith) |
| Paginated list with filters | Query |
Joins and selective projection are a read-side concern |
| Existence check before a write | Repository.findById |
Returns entity or Result.fail — not a DTO |
| Dashboard / aggregated panel | Query |
Reads across tables, no entity reconstruction needed |
Custom domain lookup (findByEmail) that feeds a command |
Repository |
Caller needs an entity to modify |
What ships with it
10 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.
- CHANGELOG.md 1008 B
- docs/i18n/README.es-ES.md 5.2 KB
- docs/i18n/README.pt-BR.md 5.1 KB
- examples/find-many-items.query.ts 504 B runs code
- examples/in-memory-find-many-items.query.ts 1.1 KB runs code
- LICENSE 1.1 KB
- package.json 800 B
- README.md 4.9 KB
- references/prisma-adapter.md 3.7 KB
- references/query-cqrs-pattern.md 5.8 KB
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.
- 2mo ago First seen · 72 lines · 80 tokens per session scan A 1a29c21b76e6
ts-query-cqrs is a skill published in the GitHub repository llodev/skills (2 stars, last pushed 12d ago), licensed MIT. It adds 80 tokens to every session and 900 once invoked, about $0.0003 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-31.
Other skills, from other repositories
adapter-express
Mount tRPC as Express middleware with createExpressMiddleware() from @trpc/server/adapters/express. Access Express req/res in createContext via CreateExpressContextOptions. Mount at a path prefix like app.use('/trpc', ...). Avoid global express.json() conflicting with tRPC body parsing for FormData.
trpc-router
Entry point for all tRPC skills. Decision tree routing by task: initTRPC.create(), t.router(), t.procedure, createTRPCClient, adapters, subscriptions, React Query, Next.js, links, middleware, validators, error handling, caching, FormData.
stripe-projects
Use after E2B sandbox/API access has been provisioned through Stripe Projects and the user needs to use the resulting E2B API key with the E2B CLI, JavaScript SDK, Python SDK, or Code Interpreter SDK.
nestjs-expert
Creates and configures NestJS modules, controllers, services, DTOs, guards, and interceptors for enterprise-grade TypeScript backend applications. Use when building NestJS REST APIs or GraphQL services, implementing dependency injection, scaffolding modular architecture, adding JWT/Passport authentication, integrating…
chat-sdk
Build multi-platform chat bots with Chat SDK (chat npm package). Use when developers want to (1) Build a Slack, Teams, Google Chat, Discord, Telegram, GitHub, Linear, or WhatsApp bot, (2) Use Chat SDK to handle mentions, direct messages, subscribed threads, reactions, slash commands, cards, modals, files, or AI…
azure-web-pubsub-ts
Build real-time messaging applications using Azure Web PubSub SDKs for JavaScript (@azure/web-pubsub, @azure/web-pubsub-client). Use when implementing WebSocket-based real-time features, pub/sub me...