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-form-data-handlinggit 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-form-data-handling)<a href="https://agentmods.dev/skills/jeffsenso/prestashop-skills/create-form-data-handling"><img src="https://agentmods.dev/badge/skills/jeffsenso/prestashop-skills/create-form-data-handling/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-form-data-handling"><img src="https://agentmods.dev/badge/skills/jeffsenso/prestashop-skills/create-form-data-handling.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.00074 | $0.00757 |
| Opus 5 | $0.00037 | $0.00378 |
| Sonnet 5 | $0.00015 | $0.00151 |
| Haiku 4.5 | $0.00007 | $0.00076 |
Grade A, and why
create-form-data-handling 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 10d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
create-form-data-handling
Read @.ai/Component/Forms/CONTEXT.md for form conventions (IdentifiableObject pattern, service registration).
1. DataProvider
Create src/Core/Form/IdentifiableObject/DataProvider/{Domain}FormDataProvider.php implementing FormDataProviderInterface:
getData(int $id): array— dispatchGet{Domain}ForEditingquery via query bus, map the result DTO to the form's expected array structuregetDefaultData(): array— return sensible defaults for the create form (empty strings, null IDs,active => true)- Both methods must return the same array structure — the form type cannot distinguish create from edit
- Multilingual fields: return arrays keyed by integer language ID
Reference: src/Core/Form/IdentifiableObject/DataProvider/TaxFormDataProvider.php (simple)
2. DataHandler
Create src/Core/Form/IdentifiableObject/DataHandler/{Domain}FormDataHandler.php implementing FormDataHandlerInterface:
create(array $data): mixed— buildAdd{Domain}Commandfrom$data, dispatch via command bus, return new entity IDupdate(int $id, array $data): void— buildEdit{Domain}Command($id), call fluent setters for each field from$data, dispatch- Map form array keys to command setters:
$command->setName($data['name']) - Multilingual:
$command->setLocalizedNames($data['name'])where value is lang-keyed array - Sub-resource commands dispatched separately (see Forms/CONTEXT.md for dispatch order)
Reference: src/Core/Form/IdentifiableObject/DataHandler/TaxFormDataHandler.php (simple)
3. Error handling
- When
!$form->isValid(), re-render the form — Twig displays errors automatically via{{ form_errors(field) }} - Error handling conventions (server-side validation as source of truth, tab error nav) are in Forms/CONTEXT.md
4. Service registration
Register in the appropriate DI YAML file:
{Domain}Type— tagged withform.type(usually auto-discovered){Domain}FormDataProvider— withautowire: true,autoconfigure: true{Domain}FormDataHandler— withautowire: true,autoconfigure: true- Service ID naming convention is in Forms/CONTEXT.md
- Verify:
php bin/console debug:container | grep {domain}_form
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.
- 10d ago First seen · 60 lines · 74 tokens per session scan A 339224283a56
create-form-data-handling is a skill published in the GitHub repository jeffsenso/prestashop-skills (5 stars, last pushed 16d ago), licensed MIT. It adds 74 tokens to every session and 757 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…
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…
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…
300-frameworks-spring-boot-create-project
Use when you need to create a new Maven-based Spring Boot 4.0.x project using SDKMAN-managed Java and Spring Boot CLI tooling. This should trigger for requests such as Create a Spring Boot Maven project; Bootstrap Spring Boot project with SDKMAN; Generate a new Spring Boot service; Create Spring Boot 4 Maven project…
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…