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 create-cqrs-queriesgit 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/create-cqrs-queries)<a href="https://agentmods.dev/skills/jeffsenso/prestashop-skills/create-cqrs-queries"><img src="https://agentmods.dev/badge/skills/jeffsenso/prestashop-skills/create-cqrs-queries/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/create-cqrs-queries"><img src="https://agentmods.dev/badge/skills/jeffsenso/prestashop-skills/create-cqrs-queries.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.00072 | $0.00591 |
| Opus 5 | $0.00036 | $0.00296 |
| Sonnet 5 | $0.00014 | $0.00118 |
| Haiku 4.5 | $0.00007 | $0.00059 |
Grade A, and why
create-cqrs-queries 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.
What it actually says
create-cqrs-queries
Read CQRS/CONTEXT.md for conventions (scalar inputs/VO getters, QueryResult scalar-only rule).
1. Get-for-editing query
Create src/Core/Domain/{Domain}/Query/Get{Domain}ForEditing.php:
- Constructor takes
int $id(scalar) - Getter returns VO:
getId(): {Domain}Id - Queries are read-only data objects — no side effects
2. Result DTO
Create src/Core/Domain/{Domain}/QueryResult/Editable{Domain}.php:
- Constructor parameters: all fields the edit form needs to pre-fill (scalar types only — see CONTEXT.md)
- Public getter for every field
- Immutable: no setters, all values set at construction
Reference: src/Core/Domain/Tax/QueryResult/EditableTax.php (simple), src/Core/Domain/Manufacturer/QueryResult/EditableManufacturer.php (with associations)
3. List query (assess first)
Most PS grids use SearchCriteria + grid QueryBuilder directly — no explicit CQRS query class needed.
Check the domain convention before creating a list query:
- If the domain uses
SearchCriteria+QueryBuilderin the grid: skip this step - If the domain uses an explicit query: create
Get{Domain}sForListing.phpwithSearchCriteriaparameter
Reference: Most domains (Tax, Manufacturer, Category) use the grid QueryBuilder pattern without an explicit list query.
4. Query handler interfaces
Create in src/Core/Domain/{Domain}/QueryHandler/:
Get{Domain}ForEditingHandlerInterfacewithhandle(Get{Domain}ForEditing $query): Editable{Domain}- If list query exists, create corresponding interface
- Query handlers always return data (typed DTO or array) — never void
Rules
Conventions (scalar-only DTOs, read-only queries) are in CQRS/CONTEXT.md. Skill-specific reminders:
- Map ALL editable fields in the DTO — missing fields cause empty form fields on edit
- Return typed DTOs, not ObjectModel instances
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 · 59 lines · 72 tokens per session scan A edfa77676b2f
create-cqrs-queries is a skill published in the GitHub repository jeffsenso/prestashop-skills (5 stars, last pushed 17d ago), licensed MIT. It adds 72 tokens to every session and 591 once invoked, about $0.0004 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…