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 byerlikaya/claude-starter-kit --skill cqrs-aop-modulegit clone --depth 1 https://github.com/byerlikaya/claude-starter-kitWrote 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/byerlikaya/claude-starter-kit/cqrs-aop-module)<a href="https://agentmods.dev/skills/byerlikaya/claude-starter-kit/cqrs-aop-module"><img src="https://agentmods.dev/badge/skills/byerlikaya/claude-starter-kit/cqrs-aop-module/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/byerlikaya/claude-starter-kit/cqrs-aop-module"><img src="https://agentmods.dev/badge/skills/byerlikaya/claude-starter-kit/cqrs-aop-module.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.00050 | $0.00949 |
| Opus 5.5 | $0.00020 | $0.00380 |
| Sonnet 5.5 | $0.00010 | $0.00190 |
| Haiku 4.5 | $0.00005 | $0.00095 |
Grade A, and why
cqrs-aop-module 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 28d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backend Pattern (MediatR CQRS / IResult / AOP)
Trigger phrases: "cqrs-aop-module", "new handler", "write a command", "add a query", "validator", "aspect"
This is the DEFAULT backend pattern, not the only one.
backend-expert-cskis pattern-neutral; it applies whichever backend-pattern skill the project ships. A project on Clean Architecture, Vertical Slice, Minimal API, or plain layered replaces this skill with its own (same format) — the agent then follows that. Nothing forces DevArch.
Kit adaptation (local, .claude/):
backend-expert-cskapplies thecqrs-aop-moduleskill. Sources (alignment): the DevArchitecture pattern — its name does NOT leak into generated code / namespace / file / comment / csproj / Swagger / JWT (§4.2). The pattern lives here; the generated artifact is written with project-specific names.
Layout
Three folders under Business/Handlers/{Entity}/: Commands/ · Queries/ · ValidationRules/.
Each request + its handler lives in a single file, nested.
Command pattern (write)
- Request class:
IRequest<IResult>(orIRequest<IDataResult<T>>if it returns data). - Handler:
IRequestHandler<TRequest, IResult>inside the outer class; dependencies via the ctor (repository, cache, mediator). - Body: write via the repository →
SaveChangesAsync()→ clear the relevant cache key →return new SuccessResult(Messages.Added).
Query pattern (read)
- Request:
IRequest<IDataResult<IEnumerable<TDto>>>/IDataResult<TDto>. - The handler fetches the data via the repository/DTO →
return new SuccessDataResult<...>(data).
Result contract (NO bare types)
- Success:
SuccessResult(message)/SuccessDataResult<T>(data, message?). - Error:
ErrorResult(message)/ErrorDataResult<T>(message). - The handler never returns a raw
T/void; alwaysIResult/IDataResult<T>.
What ships with it
1 file 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.
- 28d ago First seen · 69 lines · 50 tokens per session scan A 5cf90fe5aed6
cqrs-aop-module is a skill published in the GitHub repository byerlikaya/claude-starter-kit (24 stars, last pushed 24d ago), licensed MIT. It adds 50 tokens to every session and 949 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-09-23.
Other skills, from other repositories
sglang
Fast structured generation and serving for LLMs with RadixAttention prefix caching. Use for JSON/regex outputs, constrained decoding, agentic workflows with tool calls, or when you need 5× faster inference than vLLM with prefix sharing. Powers 300,000+ GPUs at xAI, AMD, NVIDIA, and LinkedIn.
agent-django-fastapi-expert
Specialist subagent: Django ORM, Django REST Framework, FastAPI async patterns, and Pydantic v2 specialist. Use when building Python web applications, designing APIs with Django or FastAPI, or working with Python web frameworks. Trigger phrases: Django, FastAPI, DRF, Django REST Framework, Pydantic, ORM, queryset…
microservices-architecture
Microservices architecture patterns and best practices. Use when designing distributed systems, breaking down monoliths, or implementing service communication.
authentication-patterns
OAuth 2.0, JWT, SSO, MFA, NextAuth/Clerk/Supabase Auth implementation patterns.
email-systems
Transactional email (Resend, SendGrid, SES), templates (React Email, MJML), deliverability (SPF/DKIM/DMARC), and inboxing best practices. Use when building email infrastructure, designing templates, or troubleshooting deliverability.
event-driven-architecture
Kafka, RabbitMQ, SQS/SNS, event sourcing, CQRS, saga patterns, dead letter queues, and idempotency. Use when designing asynchronous systems, implementing message-driven workflows, or building event streaming pipelines.