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 register-feature-flaggit 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/register-feature-flag)<a href="https://agentmods.dev/skills/jeffsenso/prestashop-skills/register-feature-flag"><img src="https://agentmods.dev/badge/skills/jeffsenso/prestashop-skills/register-feature-flag/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/register-feature-flag"><img src="https://agentmods.dev/badge/skills/jeffsenso/prestashop-skills/register-feature-flag.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.00044 | $0.00376 |
| Opus 5 | $0.00022 | $0.00188 |
| Sonnet 5 | $0.00009 | $0.00075 |
| Haiku 4.5 | $0.00004 | $0.00038 |
Grade A, and why
register-feature-flag 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.
What it actually says
register-feature-flag
Instructions
- Open
install-dev/data/xml/feature_flag.xml. - Add inside
<entities>:<feature_flag id="{domain}"> <stability>beta</stability> <state>0</state> <label_wording>{Domain} page</label_wording> <label_domain>Admin.{Section}.Feature</label_domain> <description_wording>Enable the new Symfony-based {domain} management page (beta).</description_wording> <description_domain>Admin.{Section}.Feature</description_domain> </feature_flag> - The
namefield (which maps to theidattribute in XML) must exactly match the_legacy_feature_flagvalues in the routing YAML. - Insert a row manually for local dev:
INSERT INTO ps_feature_flag (name, state, stability) VALUES ('{domain}', 0, 'beta'); - Enable for development:
UPDATE ps_feature_flag SET state=1 WHERE name='{domain}'; - Verify routing: visit legacy URL with flag OFF → legacy page. Enable flag → redirect to Symfony route.
Rules
Conventions (atomic commit, beta→stable lifecycle) are in Controller/CONTEXT.md. Skill-specific reminder:
- state starts as 0 — contributors enable manually; merchants never see it until GA
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.
- 12d ago First seen · 37 lines · 44 tokens per session scan A 2837ed4b26c8
register-feature-flag is a skill published in the GitHub repository jeffsenso/prestashop-skills (5 stars, last pushed 18d ago), licensed MIT. It adds 44 tokens to every session and 376 once invoked, about $0.0002 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
810-regulations-eu-mifid-ii
Use when reviewing Java enterprise evidence for MiFID II investment services, investment activities, client classification, suitability, appropriateness, order-handling evidence, best-execution evidence, algorithmic-trading governance evidence, market-access governance evidence, transaction evidence, record keeping…
812-regulations-eu-product-liability-directive
Use when reviewing, designing, or modifying Java enterprise software products, AI-enabled products, RAG assistants, AI agents, generated instructions, related services, automated updates, vulnerability handling, corrective updates, warnings, instructions, or product-safety evidence under Directive (EU) 2024/2853, the…
801-regulations-eu-ai-act
Use when reviewing, designing, or modifying Java enterprise systems that use AI, LLMs, AI agents, RAG, tool calling, workflow automation, or model-based decision support and need EU AI Act regulatory awareness. This should trigger for requests such as Review a Java AI system for EU AI Act controls; Design governance…
802-regulations-dora
Use when reviewing, designing, or modifying Java enterprise systems that may support financial entities, critical ICT services, third-party ICT provider integrations, or operational resilience obligations under DORA. This should trigger for requests such as Review a Java platform for DORA ICT risk controls; Design…
803-regulations-gdpr
Use when reviewing, designing, or modifying Java enterprise systems that process personal data and need GDPR-aware engineering controls. This should trigger for requests such as Review a Java service for GDPR privacy controls; Design data-subject rights workflows; Add retention, deletion, pseudonymization, or…
042-planning-openspec
Use when creating or updating OpenSpec artifacts from an issue, plan, approved design, ADRs, existing OpenSpec, or a valid combination. The workflow assesses reviewable scope, records source authority and derivation, handles conflicts, and prevents silent synchronization. Triggers include Create OpenSpec from an…