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-removal-issuegit 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-removal-issue)<a href="https://agentmods.dev/skills/jeffsenso/prestashop-skills/create-removal-issue"><img src="https://agentmods.dev/badge/skills/jeffsenso/prestashop-skills/create-removal-issue/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-removal-issue"><img src="https://agentmods.dev/badge/skills/jeffsenso/prestashop-skills/create-removal-issue.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.00038 | $0.00436 |
| Opus 5 | $0.00019 | $0.00218 |
| Sonnet 5 | $0.00008 | $0.00087 |
| Haiku 4.5 | $0.00004 | $0.00044 |
Grade A, and why
create-removal-issue 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.
What it actually says
create-removal-issue
Prerequisites (implicit)
- The migrated Symfony page is GA (
stability="stable",state=1) and has been stable for at least one minor release with no P1 regressions.
Instructions
- Create a GitHub issue with title:
Remove deprecated Admin{Domain}sController. - Body:
**Target:** PS X.0 **Context:** The new `{Domain}Controller` (Symfony) is GA since PS W.V (PR #YYYYY). **Prerequisites:** - [ ] GA page has been stable for ≥1 minor release with no P1 regressions - [ ] Migration guide published (release notes / dev blog) - [ ] All known modules updated (verify with ecosystem team) **Files to delete:** - `controllers/admin/Admin{Domain}sController.php` - Legacy-only service registrations referencing this controller **Files to update:** - Remove `_legacy_feature_flag: {domain}` from routing YAML once the flag entry itself is dropped - Clean up `feature_flag.xml` entry if no longer needed - Assign to the team's major release milestone.
- Tag with:
major-release,legacy-cleanup.
Rules
Conventions (timing, reference GA PR) are in Migration/CONTEXT.md. Skill-specific reminders:
- The
_legacy_controller: Admin{Domain}sattribute on routes is kept (preserves URL compatibility for legacy admin links) — do not list it as a "file to update" - Never create a PR for removal until all prerequisites in the issue are checked
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 · 47 lines · 38 tokens per session scan A abdc81ef8977
create-removal-issue is a skill published in the GitHub repository jeffsenso/prestashop-skills (5 stars, last pushed 16d ago), licensed MIT. It adds 38 tokens to every session and 436 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
add-github
Add GitHub channel integration via Chat SDK. PR and issue comment threads as conversations.
catchup
Summarize and review what changed while you were away. Use after a weekend, vacation, or flight to check missed PRs, git commits, Linear tickets, and meetings — one prioritized brief, not a firehose.
056-design-avoid-breaking-changes
Use when you need to review a plan, OpenSpec change, specification, or implementation proposal for breaking-change risk across commands, skills, generated outputs, XML sources, README/docs, tests, CI, APIs, schemas, configuration, data, migration, and release guidance. This should trigger for requests such as Review…
110-java-maven-best-practices
Use when you need to review, improve, or troubleshoot a Maven pom.xml file — including dependency management with BOMs, plugin configuration, version centralization, multi-module project structure, build profiles, or any situation where you want to align your Maven setup with industry best practices. This should…
split-and-ship
Execute an approved split plan, shipping each change group separately as its own branch and PR or as sequential commits on the current branch. Use when the user asks to "split and ship", "ship the split plan", "create separate PRs", or "split changes into branches".
work-on-ticket
Fetches Jira ticket details, creates an appropriately named branch, and initiates the task planning workflow. Use when the user says "work on [TICKETID]" or similar phrases.