agentmods.dev

cc-plugin-eval

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

A skill that routes requests to cc-plugin-eval, a local checker for Claude Code plugins and skills. It analyzes files, validates configuration, explains scores, and ranks recommended fixes.

In plain words
What is it for?
Use it to audit plugins or skills, validate manifests and hooks, investigate scores, prioritize fixes, and measure token usage.
Why use it?
It turns natural requests such as auditing an add-on or checking a manifest into the appropriate local evaluation command.

Skill for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT} variable. Also seen: reads .claude/ paths; 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

not rated 5 19d ago A scan 73 tokens original MIT
View the source file ANcpLua/ancplua-claude-plugins
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 cc-plugin-eval

README.md
[![agentmods](https://agentmods.dev/badge/skills/ancplua/ancplua-claude-plugins/cc-plugin-eval.svg)](https://agentmods.dev/skills/ancplua/ancplua-claude-plugins/cc-plugin-eval)
Your own site
<a href="https://agentmods.dev/skills/ancplua/ancplua-claude-plugins/cc-plugin-eval"><img src="https://agentmods.dev/badge/skills/ancplua/ancplua-claude-plugins/cc-plugin-eval.svg" alt="Measured on agentmods" 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,604 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.01604
Opus 5 $0.00036 $0.00802
Sonnet 5 $0.00015 $0.00321
Haiku 4.5 $0.00007 $0.00160

Measured 6d ago against content hash 812e9bf6f26a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

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 6d 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/cc-plugin-eval/SKILL.md · 98 lines

How it starts

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

cc-plugin-eval

Use this as the umbrella entrypoint for local Claude Code plugin and skill evaluation. cc-plugin-eval is deterministic, local-first, and zero-dependency.

The runnable command blocks 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.

Start Here

  1. Resolve whether the target path is a skill (contains SKILL.md), a plugin (contains .claude-plugin/plugin.json), or another local folder.
  2. If the user spoke naturally, prefer the chat-first router so they see the routed local command:
node "${CLAUDE_PLUGIN_ROOT}/scripts/cc-plugin-eval.js" start <path> --request "<user request>" --format markdown
  1. Map natural chat requests to workflows:
    • "Evaluate this plugin." -> cc-plugin-eval analyze <path> --format markdown
    • "Evaluate this skill." -> cc-plugin-eval analyze <path> --format markdown (or evaluate-skill alias)
    • "Why did this score that way?" -> cc-plugin-eval analyze <path> --format markdown
    • "What should I fix first?" -> cc-plugin-eval analyze <path> --format markdown
    • "Explain the token budget for this plugin." -> cc-plugin-eval explain-budget <path> --format markdown
    • "Validate the manifest." / "Lint this plugin." -> cc-plugin-eval validate <path> --format markdown
    • "Inspect the hooks." / "Inspect the mcp servers." -> cc-plugin-eval inspect <path> --component <name> --format markdown
    • "Measure the real token usage of this skill." -> init-benchmark then benchmark, then analyze --observed-usage, then measurement-plan
    • "Help me benchmark this plugin." -> starter benchmark flow
    • "What should I run next?" -> cc-plugin-eval start <path> --request "What should I run next?" --format markdown
  2. If the user wants a rewrite plan, route to ../improve-skill/SKILL.md. That skill produces a brief and then hands the brief to skill-creator for the actual rewrite pass.
  3. If the user wants a custom rubric, route to ../metric-pack-designer/SKILL.md.
  4. If the user names a plugin or skill instead of giving a path, resolve it locally before running commands. Prefer ~/.claude/plugins/cache/<plugin-id> for installed plugins, then any repo-local plugins/<name> or skills/<name> directory. If still ambiguous, ask one short clarifying question.
  5. When the request sounds like "give me a full analysis" rather than just "evaluate", do the fuller path:
    • run analyze
    • initialize .cc-plugin-eval/benchmark.json
    • surface the setup questions that refine the starter scenarios
    • preview the first benchmark command the user can execute next

Read the full file on GitHub · 98 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. 6d ago First seen · 98 lines · 73 tokens per session scan A 812e9bf6f26a

Subscribe to this mod's changes

cc-plugin-eval is a skill published in the GitHub repository ANcpLua/ancplua-claude-plugins (5 stars, last pushed 19d ago), licensed MIT. It adds 73 tokens to every session and 1,604 once invoked, about $0.0004 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.

Building agentsancplua-fleet
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 95 tokens