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 write-behat-scenariosgit 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/write-behat-scenarios)<a href="https://agentmods.dev/skills/jeffsenso/prestashop-skills/write-behat-scenarios"><img src="https://agentmods.dev/badge/skills/jeffsenso/prestashop-skills/write-behat-scenarios/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/write-behat-scenarios"><img src="https://agentmods.dev/badge/skills/jeffsenso/prestashop-skills/write-behat-scenarios.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.00067 | $0.01109 |
| Opus 5 | $0.00034 | $0.00554 |
| Sonnet 5 | $0.00013 | $0.00222 |
| Haiku 4.5 | $0.00007 | $0.00111 |
Grade A, and why
write-behat-scenarios 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
write-behat-scenarios
Read @.ai/Component/Behat/CONTEXT.md for conventions (stateless steps, entity references, Given/When/Then).
1. Feature file setup
Create tests/Integration/Behaviour/Features/Scenario/{Domain}/{domain}_management.feature:
@restore-all-tables-before-feature
Feature: {Domain} management
As an admin
I want to manage {domain}s
So that ...
Background:
Given shop "shop1" with name "test_shop" exists
Background section should be minimal — only shared setup that every scenario needs.
Reference: tests/Integration/Behaviour/Features/Scenario/Tax/ (simple)
2. Create scenarios
Scenario: Add a new {domain} with required fields
When I add a {domain} "ref_1" with following properties:
| name | Test {Domain} |
| active | true |
Then {domain} "ref_1" should have the following properties:
| name | Test {Domain} |
| active | true |
- Test with minimum required fields
- Test with all fields
- Assertion step independently loads the entity — stateless
3. Edit scenarios
Scenario: Edit {domain} name
Given {domain} "ref_1" exists with name "Original"
When I edit {domain} "ref_1" with following properties:
| name | Updated |
Then {domain} "ref_1" should have the following properties:
| name | Updated |
- Test partial update (only changed fields)
- Verify unchanged fields remain unchanged
4. Delete scenarios
Scenario: Delete {domain}
When I delete {domain} "ref_1"
Then {domain} "ref_1" should not exist
Scenario: Delete non-existent {domain}
When I delete {domain} "non_existent_ref"
Then I should get an error "{Domain}NotFoundException"
5. Bulk action scenarios (if bulk commands exist)
Scenario: Bulk delete {domain}s
Given the following {domain}s exist:
| reference | name |
| ref_1 | First |
| ref_2 | Second |
| ref_3 | Third |
When I bulk delete {domain}s "ref_1,ref_2"
Then {domain} "ref_1" should not exist
And {domain} "ref_2" should not exist
And {domain} "ref_3" should exist
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 · 138 lines · 67 tokens per session scan A 241b171c7bcf
write-behat-scenarios is a skill published in the GitHub repository jeffsenso/prestashop-skills (5 stars, last pushed 17d ago), licensed MIT. It adds 67 tokens to every session and 1,109 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
112-java-maven-plugins
Use when you need to add or configure Maven plugins in your pom.xml — including quality tools (enforcer, surefire, failsafe, jacoco, pitest, spotbugs, pmd), security scanning (OWASP), code formatting (Spotless), version management, container image build (Jib), build information tracking, and benchmarking (JMH) …
059-design-atdd
Use when reviewing whether an OpenSpec change's execution goal, acceptance criteria, and implementation or verification tasks are aligned. This should trigger for requests such as Review this OpenSpec change with ATDD; Check acceptance criteria against tasks; Find acceptance criteria without task coverage; Detect…
111-java-maven-dependencies
Use when you need to add or evaluate Maven dependencies that improve code quality or domain modeling — including nullness annotations (JSpecify), static analysis (Error Prone + NullAway), functional programming (VAVR), architecture testing (ArchUnit), or money and currency support (JavaMoney) — and want a…
130-java-testing-strategies
Use when you need to apply testing strategies for Java code — RIGHT-BICEP to guide test creation, A-TRIP for test quality characteristics, or CORRECT for verifying boundary conditions. This should trigger for requests such as Review Java code for testing strategies; Apply RIGHT-BICEP testing strategies in Java code…
133-java-testing-acceptance-tests
Use when you need to implement acceptance tests from maintainer-sanitized Gherkin scenario facts for framework-agnostic Java (no Spring Boot, Quarkus, Micronaut) — confirming @acceptance scenarios before coding, happy path with RestAssured, DB/Kafka test fixtures, WireMock for external REST only, and AT classes run by…
323-frameworks-spring-boot-testing-acceptance-tests
Use when you need to implement acceptance tests from maintainer-authored or maintainer-sanitized Gherkin scenario facts for Spring Boot applications — including selecting scenarios tagged @acceptance, implementing happy path tests with TestRestTemplate, @SpringBootTest, Testcontainers with @ServiceConnection for…