implement-cqrs-handlers

implement-cqrs-handlers is a skill for Claude Code, Codex from jeffsenso/prestashop-skills. It costs 64 tokens per session (1,115 once invoked), scanned A, original, MIT.

Application handlers for commands that change data and queries that read it. They pass storage work to a repository, which is the code responsible for saving and loading records.

In plain words
What is it for?
Use it to implement adding, editing, deleting, status changes, and reading domain data through command and query handlers.
Why use it?
It keeps controllers and other callers separate from database or legacy entity details and gives each operation a clear place to live.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions subagents.

Good fit Use it to implement adding, editing, deleting, status changes, and reading domain data through command and query handlers.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jeffsenso/prestashop-skills/implement-cqrs-handlers
Install

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.

Any agent
npx skills add jeffsenso/prestashop-skills --skill implement-cqrs-handlers
Clone the repo
git clone --depth 1 https://github.com/jeffsenso/prestashop-skills

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for implement-cqrs-handlers

README.md
[![agentmods](https://agentmods.dev/badge/skills/jeffsenso/prestashop-skills/implement-cqrs-handlers/github.svg)](https://agentmods.dev/skills/jeffsenso/prestashop-skills/implement-cqrs-handlers)
Your own site
<a href="https://agentmods.dev/skills/jeffsenso/prestashop-skills/implement-cqrs-handlers"><img src="https://agentmods.dev/badge/skills/jeffsenso/prestashop-skills/implement-cqrs-handlers/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.

agentmods 80×15 button for implement-cqrs-handlers

Your own site · 80×15
<a href="https://agentmods.dev/skills/jeffsenso/prestashop-skills/implement-cqrs-handlers"><img src="https://agentmods.dev/badge/skills/jeffsenso/prestashop-skills/implement-cqrs-handlers.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 64 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,115 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00064 $0.01115
Opus 5 $0.00032 $0.00558
Sonnet 5 $0.00013 $0.00223
Haiku 4.5 $0.00006 $0.00112

Measured 11d ago against content hash 03dd71c01537, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

implement-cqrs-handlers 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 11d 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.

skills/prestashop-module-development/ps9-core-ai/Component/CQRS/skills/implement-cqrs-handlers/SKILL.md · 111 lines

How it starts

The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.

implement-cqrs-handlers

Handlers live in src/Adapter/{Domain}/CommandHandler/ and QueryHandler/. See CQRS/CONTEXT.md for conventions (#[AsCommandHandler]/#[AsQueryHandler] attributes, no cross-handler calls, return types).

1. Add handler

Add{Domain}Handler.php implementing Add{Domain}HandlerInterface:

  • Inject {Domain}Repository
  • handle(Add{Domain}Command $command): {Domain}Id:
    • Construct the ObjectModel entity from command data
    • For multilingual fields, map $command->getLocalizedNames() to the lang array
    • Call $this->repository->create(...)
    • Return the new {Domain}Id
  • Catch persistence exceptions, rethrow as domain exceptions

Reference: src/Adapter/Tax/CommandHandler/AddTaxHandler.php (simple), src/Adapter/Manufacturer/CommandHandler/AddManufacturerHandler.php (with image)

2. Edit handler (partial-update)

Edit{Domain}Handler.php implementing Edit{Domain}HandlerInterface:

  • Load entity: $entity = $this->repository->get{Domain}($command->getId())
  • For each field: if ($command->getName() !== null) { $entity->name = $command->getName(); }
  • Apply only non-null fields — never overwrite with null
  • Call $this->repository->update($entity)
  • Sub-resource commands are dispatched independently, not composed here

Reference: src/Adapter/Tax/CommandHandler/EditTaxHandler.php (simple), src/Adapter/Carrier/CommandHandler/EditCarrierHandler.php (many fields)

3. Delete handler

Delete{Domain}Handler.php implementing Delete{Domain}HandlerInterface:

  • Load entity to verify existence (throws {Domain}NotFoundException)
  • Check business constraints: if entity is referenced by active orders/other entities, throw CannotDelete{Domain}Exception
  • Call $this->repository->delete($command->getId())

4. Toggle status handler

Toggle{Domain}StatusHandler.php:

  • Load entity by ID
  • Flip: $entity->active = !$entity->active
  • Call repository update
  • Return void — the controller reads back state from the grid

Read the full file on GitHub · 111 lines

Changes

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.

  1. 11d ago First seen · 111 lines · 64 tokens per session scan A 03dd71c01537

Subscribe to this mod's changes

implement-cqrs-handlers is a skill published in the GitHub repository jeffsenso/prestashop-skills (5 stars, last pushed 17d ago), licensed MIT. It adds 64 tokens to every session and 1,115 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-31.

Related

Other skills, from other repositories

806-regulations-eu-data-act

Use when reviewing, designing, or modifying Java enterprise systems that expose, exchange, store, process, export, or port data across users, businesses, connected products, cloud providers, APIs, event streams, AI data pipelines, data spaces, or SaaS platforms and need EU Data Act engineering controls. This should…

jabrena/plinth · 139 tokens

031-architecture-adr-functional-requirements

Facilitates conversational discovery to create Architectural Decision Records (ADRs) for functional requirements covering CLI, REST/HTTP APIs, or both. Use when the user wants to document command-line or HTTP service architecture, capture functional requirements, create ADRs for CLI or API projects, or design…

jabrena/plinth · 115 tokens

123-java-design-patterns

Use when you need to select, review, or implement Java design and integration patterns — including classic Java design patterns, REST API patterns, Kafka and event-driven patterns, database and persistence patterns, and cross-cutting integration patterns. This should trigger for requests such as Apply Java design…

jabrena/plinth · 89 tokens

125-java-concurrency

Use when you need to apply Java concurrency best practices — including thread safety fundamentals, ExecutorService thread pool management, concurrent design patterns like Producer-Consumer, asynchronous programming with CompletableFuture, immutability and safe publication, deadlock avoidance, virtual threads…

jabrena/plinth · 133 tokens

301-frameworks-spring-boot-core

Use when you need to review, improve, or build Spring Boot 4.0.x applications — including proper usage of @SpringBootApplication, component annotations (@Controller, @Service, @Repository), bean definition and scoping, configuration classes and @ConfigurationProperties (with @Validated), component scanning…

jabrena/plinth · 165 tokens

302-frameworks-spring-boot-rest

Use when you need to design, review, or improve REST APIs with Spring Boot — including HTTP methods, resource URIs, status codes, DTOs, versioning, deprecation and sunset headers, content negotiation (JSON and vendor media types), ISO-8601 instants in DTOs, pagination/sorting/filtering, Bean Validation at the…

jabrena/plinth · 177 tokens