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 agentmods add skills/mocraimer/mo-cc-plugins/check-pluginsnpx skills add mocraimer/mo-cc-plugins --skill check-pluginsgit clone --depth 1 https://github.com/mocraimer/mo-cc-pluginsWhat 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 | $0.00052 | $0.01190 |
| Opus 5 | $0.00026 | $0.00595 |
| Sonnet 5 | $0.00010 | $0.00238 |
| Haiku 4.5 | $0.00005 | $0.00119 |
Grade A, and why
check-plugins 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 yesterday.
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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plugin Health Monitor
You are a plugin health monitor running as a recurring /loop iteration. Your job: scan installed plugins, validate their structure, check for marketplace updates, classify findings by severity, and only alert on changes since the last check.
State Management
State file: ~/.claude/loop-recipes/check-plugins-state.md
On Start — Read State
-
Read
~/.claude/loop-recipes/check-plugins-state.md. If it does not exist, initialize:--- status: idle last_check: "1970-01-01T00:00:00Z" previous_findings: [] --- # Plugin Health Log -
If
status: in-progresswith alocked_byfield set:- If
locked_bytimestamp is less than 2 hours old: a previous iteration is still running. Output "Previous iteration still running — skipping." and stop. - If
locked_byis older than 2 hours: treat as stale lock (previous iteration likely crashed), clear it, and proceed.
- If
-
Set
locked_by: <current_timestamp>andstatus: in-progress. -
Ensure
~/.claude/loop-recipes/directory exists (mkdir -p).
On End — Write State
After every iteration:
- Clear
locked_by, setstatus: idle - Update
last_checktimestamp - Store current findings as
previous_findingsfor delta comparison next time - Append iteration summary to log section
Iteration Logic
Step 1: Discover Installed Plugins
Scan the plugin cache directory:
ls -d ~/.claude/plugins/cache/*/* 2>/dev/null
For each installed plugin directory, read its plugin.json (or .claude-plugin/plugin.json). Build an inventory:
- Plugin name
- Installed version
- Plugin path
- List of declared skills, agents, hooks (from plugin.json or directory scan)
If no plugins are installed: output "No plugins installed." Stop.
Step 2: Check for Marketplace Updates
Scan marketplace sources:
ls -d ~/.claude/plugins/marketplaces/*/ 2>/dev/null
For each marketplace, check if any installed plugin has a newer version available by comparing the installed plugin's version against the marketplace's listing. Read marketplace manifests (e.g., marketplace.json) to find available versions.
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.
- yesterday First seen · 143 lines · 52 tokens per session scan A 790ad3ee205b
check-plugins is a skill published in the GitHub repository mocraimer/mo-cc-plugins (2 stars, last pushed 5mo ago), licensed MIT. It adds 52 tokens to every session and 1,190 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…