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 a8cteam51/claude-code-plugins --skill vip-plugin-updatesgit clone --depth 1 https://github.com/a8cteam51/claude-code-pluginsWrote 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/a8cteam51/claude-code-plugins/vip-plugin-updates)<a href="https://agentmods.dev/skills/a8cteam51/claude-code-plugins/vip-plugin-updates"><img src="https://agentmods.dev/badge/skills/a8cteam51/claude-code-plugins/vip-plugin-updates/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/a8cteam51/claude-code-plugins/vip-plugin-updates"><img src="https://agentmods.dev/badge/skills/a8cteam51/claude-code-plugins/vip-plugin-updates.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.00152 | $0.03189 |
| Opus 5.5 | $0.00061 | $0.01276 |
| Sonnet 5.5 | $0.00030 | $0.00638 |
| Haiku 4.5 | $0.00015 | $0.00319 |
Grade A, and why
vip-plugin-updates 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 26d 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 — 271 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VIP plugin updates
VIP sites deploy from a repository, and on these repos every plugin is vendored
in git. Updating a plugin means committing its new files - there is no other
mechanism. The VIP dashboard's plugin-update PR generator only works for repos
inside the wpcomvip organisation, so on repos owned elsewhere (for example
Automattic/store.a8c.com) that job is done here instead.
The division of labour. The person downloads the plugin zips - most are premium, behind a WooCommerce.com or vendor login - and drops them in a folder. They also merge the pull requests and test the site. Everything between those two points is yours: unpack, compare versions, swap the files, branch, commit, push, open one pull request per plugin, and sort out whatever is malformed.
One pull request per plugin. Never batch them together unless explicitly asked. A plugin that breaks the site is then one revert, not an unpicking job.
The branch decides what gets updated, not the drop folder. The zips are candidates; the list of plugins is whatever the target branch already carries. A staged plugin the branch does not track is skipped - not added, not offered as a new install. Branches legitimately carry different plugin sets, so the same drop folder produces different work against the testing branch and production.
"Already there" means git tracks files for it on that branch, not that a
directory of that name exists on disk. A checkout of another branch leaves
directories behind - on store.a8c.com, plugins/redirection/ sits on disk
while on develop holding nothing but a stray .DS_Store, because the plugin
lives on master only. The tooling asks git; so should you.
What you need before starting
- The drop folder - zips and/or already-unpacked plugin folders. Ask for the path if it was not given.
- A local working copy of the repo. Ask for the path, or find it (commonly
~/GitHub/<repo-name>). Do not clone into a temp directory without asking - the user may have local work in theirs. - Which pass this is - the testing branch (first pass) or production (second pass, after they have merged and tested). Default to the testing branch unless the branch is named or the drop folder holds a run summary from an earlier pass.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 26d ago First seen · 271 lines · 152 tokens per session scan A fa5e92fa9494
vip-plugin-updates is a skill published in the GitHub repository a8cteam51/claude-code-plugins (5 stars, last pushed 2d ago), licensed MIT. It adds 152 tokens to every session and 3,189 once invoked, about $0.0006 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-20.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
repo-sync
Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…
git-commit-writer
Trigger when the user asks to write a commit message, generate a commit from staged changes, review a diff before committing, or says "/commit". Reads git diff --staged and produces an opinionated, convention-matching commit message.