agentmods.dev

promote-feature-flag-to-stable

promote-feature-flag-to-stable is a skill for Claude Code, Codex from jeffsenso/prestashop-skills. It costs 65 tokens per session (465 once invoked), scanned A, original, MIT.

A workflow for changing a PrestaShop feature flag from beta, an early release state, to stable, the default production state, and updating browser tests accordingly.

In plain words
What is it for?
Promoting the flag, removing flag-enabling calls from Playwright tests, changing old controller URLs to Symfony routes, and running the campaign suite.
Why use it?
It makes the feature available by default only after stability checks, while ensuring tests no longer depend on manually enabling the flag.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

not rated 5repo 18d ago A scan 65 tokens original MIT

Good fit Promoting the flag, removing flag-enabling calls from Playwright tests, changing old controller URLs to Symfony routes, and running the campaign suite.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jeffsenso/prestashop-skills/promote-feature-flag-to-stable
View source ↗ jeffsenso/prestashop-skills
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 promote-feature-flag-to-stable
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 promote-feature-flag-to-stable

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/jeffsenso/prestashop-skills/promote-feature-flag-to-stable"><img src="https://agentmods.dev/badge/skills/jeffsenso/prestashop-skills/promote-feature-flag-to-stable.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 65 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 465 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.00065 $0.00465
Opus 5 $0.00032 $0.00233
Sonnet 5 $0.00013 $0.00093
Haiku 4.5 $0.00006 $0.00047

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

Security

Grade A, and why

promote-feature-flag-to-stable 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 12d 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/Migration/skills/promote-feature-flag-to-stable/SKILL.md · 44 lines

What it actually says

promote-feature-flag-to-stable

Prerequisite

The feature flag must already exist (registered earlier as beta). This skill only promotes it; it does not create it.

1. Promote the feature flag

  1. Verify GA prerequisites: page is stable, no P1 regressions in the last release.
  2. Open install-dev/data/xml/feature_flag.xml
  3. Find the {domain} entry
  4. Change <stability>beta</stability> to <stability>stable</stability>
  5. Change <state>0</state> to <state>1</state>
  6. After merging: verify the flag is stable/state=1 in a fresh install

2. Migrate Playwright tests to default

In the same PR (or immediately after):

  1. For each Playwright campaign file:
    • Remove enableFeatureFlag('{domain}') calls from before() / beforeAll
    • Replace any legacy index.php?controller=Admin{Domain}s URLs with Symfony route paths
    • Update page object imports if HTML structure changed
  2. Run the full campaign suite without the flag enable — all must pass
  3. Remove the enableFeatureFlag call completely — do not leave it commented out

Rules

  • GA PR contains ONLY the flag promotion + test migration — zero feature changes
  • Promote in a dedicated PR so it can be reverted instantly if a critical bug is found
  • stability=stable + state=1: stable = shown in admin panel, state=1 = enabled by default
  • Do not change any other flag entry in the file
  • Playwright test suite must remain green after removing the flag enable
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. 12d ago First seen · 44 lines · 65 tokens per session scan A 41da12ff8fb4

Subscribe to this mod's changes

promote-feature-flag-to-stable is a skill published in the GitHub repository jeffsenso/prestashop-skills (5 stars, last pushed 18d ago), licensed MIT. It adds 65 tokens to every session and 465 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.

E2E testingTestingagent-skillsclaude-skillscopilot-skillsgithub-copilotprestashopprestashop-module
Related

Other skills, from other repositories

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…

jabrena/plinth · 142 tokens

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…

jabrena/plinth · 156 tokens

423-frameworks-quarkus-testing-acceptance-tests

Use when you need to implement acceptance tests from maintainer-sanitized Gherkin scenario facts for Quarkus applications — including @acceptance scenarios, @QuarkusTest, BaseAcceptanceTest with QuarkusTestResourceLifecycleManager for Testcontainers and WireMock, REST Assured for full HTTP pipeline testing, WireMock…

jabrena/plinth · 219 tokens

132-java-testing-integration-testing

Use when you need to set up, review, or improve Java integration tests — including generating a BaseIntegrationTest.java with WireMock for HTTP stubs, detecting HTTP client infrastructure from import signals, injecting service coordinates dynamically via System.setProperty(), creating WireMock JSON mapping files with…

jabrena/plinth · 155 tokens

322-frameworks-spring-boot-testing-integration-tests

Use when you need to write or improve integration tests — including Testcontainers with @ServiceConnection, @DataJdbcTest persistence slices, TestRestTemplate or MockMvcTester for HTTP, data isolation, and container lifecycle management for Spring Boot 4.0.x. This should trigger for requests such as Review Java code…

jabrena/plinth · 123 tokens

422-frameworks-quarkus-testing-integration-tests

Use when you need to write or improve integration tests for Quarkus — including @QuarkusTest, Dev Services for automatic container provisioning, Testcontainers via QuarkusTestResourceLifecycleManager, WireMock for external HTTP stubs, @QuarkusIntegrationTest for black-box testing against packaged artifacts, REST…

jabrena/plinth · 190 tokens