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.
/plugin marketplace add ANcpLua/ancplua-claude-plugins/plugin install cc-plugin-evalWrote 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/ancplua/ancplua-claude-plugins/evaluate-skill)<a href="https://agentmods.dev/skills/ancplua/ancplua-claude-plugins/evaluate-skill"><img src="https://agentmods.dev/badge/skills/ancplua/ancplua-claude-plugins/evaluate-skill.svg" alt="Measured on agentmods" 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.00075 | $0.01303 |
| Opus 5 | $0.00037 | $0.00651 |
| Sonnet 5 | $0.00015 | $0.00261 |
| Haiku 4.5 | $0.00007 | $0.00130 |
Grade A, and why
evaluate-skill 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 7d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Evaluate Skill
Use this skill when the target is a local skill directory or a SKILL.md file. cc-plugin-eval handles the structural and budget signals deterministically without an LLM. If the user wants an LLM-graded rubric or a rewrite pass, hand off to the skill-creator skill (Anthropic's skill-creator@claude-plugins-official) - that skill specializes in single-skill grading and rewrites, while cc-plugin-eval focuses on structural and budget signals.
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.
Workflow
- Treat "Evaluate this skill." as the default entrypoint.
- If the user names a skill instead of giving a path, resolve it locally first. Prefer
~/.claude/plugins/cache/<plugin-id>/skills/<skill-name>for installed-plugin skills, then any repo-localskills/<skill-name>directory. If the name is still ambiguous, ask one short clarifying question before running commands. - If the user says the request in natural language first, run
cc-plugin-eval start <skill-path> --request "<user request>" --format markdownto show the routed path clearly. - Run
cc-plugin-eval analyze <skill-path> --format markdown. The convenience aliascc-plugin-eval evaluate-skill <skill-path>returns the same payload but errors out if the path is not a skill. - Review
At a Glance,Why It Matters,Fix First, andRecommended Next Stepbefore drilling into details. - Explain which findings are structural (frontmatter validity, file size, broken links), which are budget-related (trigger / invoke / deferred), and which are best-practice (allowed-tools syntax, progressive disclosure).
- If the user asks for an "analysis" of the skill, do not stop at the report. Also run
cc-plugin-eval init-benchmark <skill-path>and show the setup questions for refining the starter scenarios in.cc-plugin-eval/benchmark.json. - If the user wants real usage numbers, switch to "Measure the real token usage of this skill." and run the benchmark flow.
- After observed usage is available, use
cc-plugin-eval measurement-plan <skill-path> --observed-usage <usage.jsonl> --format markdownto recommend what to instrument next. - If the user wants a rewrite plan, route to
../improve-skill/SKILL.md. That skill writes a brief and hands it toskill-creatorfor the actual rewrite.
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.
- 7d ago First seen · 63 lines · 75 tokens per session scan A 8edd2afb6802
evaluate-skill is a skill published in the GitHub repository ANcpLua/ancplua-claude-plugins (5 stars, last pushed 20d ago), licensed MIT. It adds 75 tokens to every session and 1,303 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
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…
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…