Borrowing it
Nothing to install: this file belongs to WPDevelopers/essential-addons-for-elementor-lite. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/WPDevelopers/essential-addons-for-elementor-lite/master/.claude/skills/release-checklist/SKILL.mdgit clone --depth 1 https://github.com/WPDevelopers/essential-addons-for-elementor-liteWrote 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/wpdevelopers/essential-addons-for-elementor-lite/release-checklist)<a href="https://agentmods.dev/skills/wpdevelopers/essential-addons-for-elementor-lite/release-checklist"><img src="https://agentmods.dev/badge/skills/wpdevelopers/essential-addons-for-elementor-lite/release-checklist/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/wpdevelopers/essential-addons-for-elementor-lite/release-checklist"><img src="https://agentmods.dev/badge/skills/wpdevelopers/essential-addons-for-elementor-lite/release-checklist.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.00083 | $0.01635 |
| Opus 5.5 | $0.00033 | $0.00654 |
| Sonnet 5.5 | $0.00017 | $0.00327 |
| Haiku 4.5 | $0.00008 | $0.00163 |
Grade A, and why
release-checklist 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 1mo 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 1mo ago First seen · 118 lines · 83 tokens per session scan A 425f726922c1
release-checklist is a skill published in the GitHub repository WPDevelopers/essential-addons-for-elementor-lite (53 stars, last pushed today), with no licence file. It adds 83 tokens to every session and 1,635 once invoked, about $0.0003 per session on Opus 5.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-09-04.
Other skills, from other repositories
version-management
Guide to managing the WP Rig framework version and the theme version independently.
pre-release
Runs the pre-release checklist. Sets the readme.txt Stable tag to the version being released, captures every page type (sitemaps, robots, feeds, and the rest of the catalog), and flicks all buttons that the changelog mentions. Use when preparing a release, shipping a WordPress.org update, or when the user asks for the…
wp-org-submission
Use when submitting a WordPress plugin to the WP.org directory for the first time, deploying a new version via SVN (plugins.svn.wordpress.org trunk, tags, assets), fixing a reviewer rejection (17-issue catalog with exact reviewer quotes), writing or correcting readme.txt (Stable tag, Changelog, Upgrade Notice…
emdash-github-actions
Sets up GitHub Actions CI/CD workflows for EmDash plugins — TypeScript type-checking, ESLint linting, Vitest testing, npm publishing, and automated releases. ALWAYS use this skill when a user wants to create, add, set up, or configure GitHub Actions, CI/CD, automated checks, or deployment workflows for an EmDash…
github-repo
Audits and improves GitHub repository quality — README structure, community health files, .github directory setup, issue/PR templates, metadata, releases, and branch hygiene. Use this skill whenever the user asks to improve, audit, review, or set up a GitHub repository, or when they mention things like "make my repo…
wp-plugin-release
Use when bumping a WordPress plugin version or cutting a release — syncing version across all sources: plugin header (Version: X.Y.Z), version constant (define MYPLUGINVERSION), readme.txt (Stable tag + Changelog + Upgrade Notice), CHANGELOG.md, and .pot Project-Id-Version; following semver (major/minor/patch) rules…