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-prgit 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-pr)<a href="https://agentmods.dev/skills/jeffsenso/prestashop-skills/create-pr"><img src="https://agentmods.dev/badge/skills/jeffsenso/prestashop-skills/create-pr/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-pr"><img src="https://agentmods.dev/badge/skills/jeffsenso/prestashop-skills/create-pr.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.00045 | $0.00589 |
| Opus 5 | $0.00023 | $0.00295 |
| Sonnet 5 | $0.00009 | $0.00118 |
| Haiku 4.5 | $0.00005 | $0.00059 |
Grade A, and why
create-pr 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 9d 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create a PrestaShop Pull Request
Purpose
Guide a contributor through creating a pull request that complies with the PrestaShop contribution guidelines, including the mandatory metadata table.
Steps
1. Gather context
- Read the PR template from
.github/PULL_REQUEST_TEMPLATE.md— this is the single source of truth for the table format. - Run
git logandgit diffagainst the target branch to understand what changed. - Identify the target branch from git (see branching rules in
.ai/CONTEXT.md).
2. Auto-fill fields
From code analysis and git context, infer as much as possible:
| Field | How to infer |
|---|---|
| Branch | Current git branch or merge target |
| Description | Summarize from commits and diff. Be specific (versions, browser/server config, module/theme). |
| Type | bug fix · improvement · new feature · refacto — infer from changes |
| Category | FO · BO · CO · IN · WS · TE · LO · ME · PM — infer from files changed. See category reference. |
| BC breaks | Analyze public API changes → yes / no |
| Deprecations | Check for new @deprecated annotations → yes / no |
| How to test | Write step-by-step verification instructions from the PR context |
| Fixed issue | Extract from conversation, branch name (e.g. fix/12345), or commit messages. Format: Fixes #<number> |
3. Ask before guessing
For any required field (Branch, Description, Type, Category, BC breaks, Deprecations) that cannot be confidently determined, ask the user. Do not guess.
Optional fields (UI Tests, Related PRs, Sponsor company) — fill when known, leave the template placeholder otherwise.
4. Create the PR
Use GitHub MCP tools (mcp__github__create_pull_request) or gh pr create CLI to create the PR with the filled-in template as the body.
Output
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.
- 9d ago First seen · 52 lines · 45 tokens per session scan A 7c1f8d22b988
create-pr is a skill published in the GitHub repository jeffsenso/prestashop-skills (5 stars, last pushed 15d ago), licensed MIT. It adds 45 tokens to every session and 589 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
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…
gh-address-comments
Fetch all review comments and threads on the current branch's open GitHub PR using the gh CLI, present a numbered summary, and address the ones the user selects.
git-workflow
A guide for handling Git repository work safely, including status checks, branches, commits, pushes, pull requests, and rebasing. Git is a version-control system that records code changes and coordinates work between developers.
spk-gate-merge
Merge an accepted Spec Kitty mission safely, preserving git invariants, mission state, and post-merge follow-through.
accessing-github-repos
GitHub repository access in containerized environments using REST API and credential detection. Use when git clone fails, or when accessing private repos/writing files via API.
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…