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 skills add ai-plugin-marketplace/template --skill evaluate-skillgit clone --depth 1 https://github.com/ai-plugin-marketplace/templateWrote 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/ai-plugin-marketplace/template/evaluate-skill)<a href="https://agentmods.dev/skills/ai-plugin-marketplace/template/evaluate-skill"><img src="https://agentmods.dev/badge/skills/ai-plugin-marketplace/template/evaluate-skill/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.
<a href="https://agentmods.dev/skills/ai-plugin-marketplace/template/evaluate-skill"><img src="https://agentmods.dev/badge/skills/ai-plugin-marketplace/template/evaluate-skill.svg" alt="Reviewed on agentmods" width="80" 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.00016 | $0.00475 |
| Opus 5.5 | $0.00006 | $0.00190 |
| Sonnet 5.5 | $0.00003 | $0.00095 |
| Haiku 4.5 | $0.00002 | $0.00047 |
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 1mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- evaluate-skill — 100% identical, 0 lines differ
What it actually says
Evaluate Skill
Orchestrate a cross-tier evaluation of an AI skill to determine its clarity and robustness.
Procedure
-
Load inputs
- Read the skill file at
{{ skill-path }} - Read the test cases file at
{{ test-cases-path }} - Validate that test cases is a JSON array of objects with
inputandexpectedOutcomefields
- Read the skill file at
-
Set up evaluation matrix
- Model tiers to test:
opus,sonnet,haiku - For each tier, for each test case: plan one blind test run
- Model tiers to test:
-
Execute blind tests (highest tier first)
- For each model tier (opus → sonnet → haiku):
- For each test case:
- Spawn a test-subject agent at the current tier
- Provide it ONLY the skill content and the test case
input - Do NOT provide the
expectedOutcometo the test subject - Collect the test subject's output
- For each test case:
- For each model tier (opus → sonnet → haiku):
-
Evaluate results
- For each test run, compare the test subject's output against the
expectedOutcome - Determine pass/fail using semantic similarity (the output need not be identical, but must achieve the same goal)
- Record: tier, test case index, pass/fail, output summary
- For each test run, compare the test subject's output against the
-
Generate refinement report
- Identify the lowest tier where all test cases pass ("clarity floor")
- For each failure, analyze WHY the lower-tier agent failed:
- Ambiguous instructions?
- Missing context or assumptions?
- Overly complex multi-step reasoning?
- Implicit knowledge requirements?
- Produce specific, actionable recommendations to improve the skill
- Format as a structured report with sections: Summary, Per-Tier Results, Failure Analysis, Recommendations
-
Output the report to the user
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.
- 1mo ago First seen · 52 lines · 16 tokens per session scan A a72958959a4d
evaluate-skill is a skill published in the GitHub repository ai-plugin-marketplace/template (11 stars, last pushed 4mo ago), licensed MIT. It adds 16 tokens to every session and 475 once invoked, about $0.0001 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.
Other skills, from other repositories
kiro-validate-impl
Validate feature-level integration after all tasks are implemented. Checks cross-task consistency, full test suite, and overall spec coverage.
kiro-impl
Implement approved tasks using TDD with subagent dispatch. Runs all pending tasks autonomously or selected tasks manually.
writing-livekit-scenarios
Creates and maintains the scenarios a LiveKit agent simulation runs, and wires the agent to consume them. Use when the user asks "what should I test", "generate simulation scenarios", "write scenarios for my agent", "add a scenario for X", "organize my scenario files", "my simulations are flaky", "the scenario hits my…
debugging-livekit-agents
Drives a live multi-turn conversation with a LiveKit agent running locally, using lk agent debugger. Use when the user says "test my agent", "try my agent", "does this work", or "why did it call that tool", after editing an agent to check how it behaves, or when an agent on a speech-to-speech model or one that…
running-livekit-simulations
Runs LiveKit agent simulations and acts on the results. Use when the user says "run my simulations", "regression test my agent before deploying", "run the scenarios", "use lk agent simulate", "did my agent pass", "why did this scenario fail", "run simulations in CI", "test the audio pipeline", "check turn-taking and…
ui-regression
This skill should be used when the user asks to "verify UI changes", "audit UI quality", "test every screen and action", "run regression QA", "check a deployed UI", or "validate an extension release". Test known web and browser-extension workflows on localhost, staging, or production with action coverage, recovery…