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 jeffsenso/prestashop-skills --skill implement-cqrs-handlersgit clone --depth 1 https://github.com/jeffsenso/prestashop-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/jeffsenso/prestashop-skills/implement-cqrs-handlers)<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.
<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>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.00064 | $0.01115 |
| Opus 5 | $0.00032 | $0.00558 |
| Sonnet 5 | $0.00013 | $0.00223 |
| Haiku 4.5 | $0.00006 | $0.00112 |
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.
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
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.
- 11d ago First seen · 111 lines · 64 tokens per session scan A 03dd71c01537
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.
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…
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…
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…
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…
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…
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…