What is cc-plugin-eval?

A local command-line checker for Claude Code plugins and skills. It examines their files and configuration, measures token use, assigns scores, compares add-ons, and can run benchmarks with Claude.

Use it to inspect manifests, hooks, MCP and agent settings, compare plugins, create improvement briefs, and check real token usage.

It helps find configuration and design problems before an add-on is used, and shows which improvements should come first.

cc-plugin-eval — Plugin by ANcpLua

Install

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.

Claude Code

/plugin marketplace add ANcpLua/ancplua-claude-plugins

agentmods

npx agentmods add plugins/ancplua/ancplua-claude-plugins/cc-plugin-eval

Clone the repo

git clone --depth 1 https://github.com/ANcpLua/ancplua-claude-plugins

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.

When invoked not measured Not applicable: nothing here is loaded into a session.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Security

Grade A, and why

cc-plugin-eval 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 2d 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/.claude-plugin/plugin.json · 27 lines

What it actually says

{
  "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
  "name": "cc-plugin-eval",
  "version": "0.2.5",
  "description": "Local-first CLI to evaluate Claude Code plugins and skills: token-budget analysis, manifest/hook/MCP/agent linting, scoring, comparison, improvement briefs, and real claude benchmarking.",
  "author": {
    "name": "ANcpLua",
    "url": "https://github.com/ANcpLua"
  },
  "homepage": "https://github.com/ANcpLua/ancplua-claude-plugins/tree/main/plugins/cc-plugin-eval",
  "repository": "https://github.com/ANcpLua/ancplua-claude-plugins",
  "license": "MIT",
  "keywords": [
    "claude-code",
    "plugin",
    "skill",
    "evaluation",
    "quality",
    "token-budget",
    "lint",
    "manifest",
    "hooks",
    "mcp",
    "lsp"
  ]
}

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.

2d ago First seen · 27 lines scan A 729ed7ba1b8b

Subscribe to this mod's changes

cc-plugin-eval is a plugin published in the GitHub repository ANcpLua/ancplua-claude-plugins (5 stars, last pushed 15d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.

ancplua-fleet

cc-plugin-eval

Getting it into your agent

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other plugins, from other repositories

humanizer

nextjs

nextjs

claude-plugins-official

knowledge-work-plugins

ecc