evaluate-plugin

evaluate-plugin is a skill for Claude Code from ANcpLua/ancplua-claude-plugins. It costs 73 tokens per session (1,480 once invoked), scanned A, original, MIT.

A checker for a local Claude Code plugin bundle, identified by a .claude-plugin/plugin.json manifest file. It reviews the bundle's configuration and included components.

In plain words
What is it for?
Use it to audit, validate, lint, inspect, or benchmark a plugin, then rank the fixes that matter most.
Why use it?
It finds manifest errors, problems in hooks or servers, and other issues before the plugin is used or shared.

Skill for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT} variable. Also seen: mentions .claude-plugin; mentions Claude Code.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the cc-plugin-eval plugin — 5 skills shipped together

Good fit Use it to audit, validate, lint, inspect, or benchmark a plugin, then rank the fixes that matter most.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add ANcpLua/ancplua-claude-plugins
Claude Code
/plugin install cc-plugin-eval

Made for: Claude Code.

Or install cc-plugin-eval, the plugin that ships this one along with the rest of its 5 skills.

Wrote 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.

agentmods badge for evaluate-plugin

README.md
[![agentmods](https://agentmods.dev/badge/skills/ancplua/ancplua-claude-plugins/evaluate-plugin/github.svg)](https://agentmods.dev/skills/ancplua/ancplua-claude-plugins/evaluate-plugin)
Your own site
<a href="https://agentmods.dev/skills/ancplua/ancplua-claude-plugins/evaluate-plugin"><img src="https://agentmods.dev/badge/skills/ancplua/ancplua-claude-plugins/evaluate-plugin/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.

agentmods 80×15 button for evaluate-plugin

Your own site · 80×15
<a href="https://agentmods.dev/skills/ancplua/ancplua-claude-plugins/evaluate-plugin"><img src="https://agentmods.dev/badge/skills/ancplua/ancplua-claude-plugins/evaluate-plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 73 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,480 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00073 $0.01480
Opus 5.5 $0.00029 $0.00592
Sonnet 5.5 $0.00015 $0.00296
Haiku 4.5 $0.00007 $0.00148

Measured 2mo ago against content hash 737db7074db0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

evaluate-plugin 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 2mo 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.

plugins/cc-plugin-eval/skills/evaluate-plugin/SKILL.md · 79 lines

How it starts

The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Evaluate Plugin

Use this skill when the target is a plugin root with .claude-plugin/plugin.json. If the target is a single SKILL.md directory, hand off to ../evaluate-skill/SKILL.md instead.

The runnable commands below invoke the shipped script through the plugin root, which works in any checkout: node "${CLAUDE_PLUGIN_ROOT}/scripts/cc-plugin-eval.js" <command> <args>. Inline mentions of cc-plugin-eval <command> are shorthand for that same invocation; the bare cc-plugin-eval alias only exists if you ran npm link in the plugin directory.

When To Use

  • The path passed by the user contains .claude-plugin/plugin.json.
  • The user's question is about the bundle as a whole, not a single skill.
  • The user says "audit", "validate", "lint", "inspect", or "benchmark this plugin".

If the path is a SKILL.md or a directory holding one, route to ../evaluate-skill/SKILL.md. If the path contains neither, treat it as a generic directory and run cc-plugin-eval analyze <path> to surface the file-level signals.

Workflow

  1. Treat "Evaluate this plugin." as the default entrypoint.
  2. If the request comes in as natural chat language, run cc-plugin-eval start <plugin-root> --request "<user request>" --format markdown first so the user sees the routed local path.
  3. Run cc-plugin-eval analyze <plugin-root> --format markdown.
  4. Read Fix First before drilling into manifest findings, hook findings, MCP/LSP findings, monitor/agent findings, marketplace findings, then nested skill findings.
  5. If the plugin contains multiple skills, summarize the strongest and weakest ones explicitly.
  6. If the user wants a CI-friendly pass/fail check, run cc-plugin-eval validate <plugin-root> --strict. Exit code 2 means at least one warn or fail finding fired.
  7. If the user wants component-only output (only hooks, only mcp, etc.), run cc-plugin-eval inspect <plugin-root> --component <name>.
  8. If the user wants measured usage, switch to "Help me benchmark this plugin." and use the starter benchmark flow.
  9. If the user wants trend data, compare two JSON outputs with cc-plugin-eval compare before.json after.json.

Read the full file on GitHub · 79 lines

Changes

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.

  1. 2mo ago First seen · 79 lines · 73 tokens per session scan A 737db7074db0

Subscribe to this mod's changes

evaluate-plugin is a skill published in the GitHub repository ANcpLua/ancplua-claude-plugins (6 stars, last pushed 2d ago), licensed MIT. It adds 73 tokens to every session and 1,480 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-08-31.

Related

evaluate-plugin compared with skills from other repositories

evaluate-plugin next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
evaluate-pluginANcpLua/ancplua-claude-pluginsSkill62d agoMITA73Claude Code
imagegenopenai/codexSkill135ktodayApache-2.0A113Codex
playwright-climicrosoft/playwrightSkill100kyesterdayApache-2.0A19Claude Code
browser-automationopenclaw/openclawSkill394ktodayMITA36Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79k4d agoMITA200Claude Code, Codex
systematic-debuggingobra/superpowersSkill316k7d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143ktodayMITA95Claude Code