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 agentmods add skills/8090-inc/software-factory-plugin/evaluate-skillnpx skills add 8090-inc/software-factory-plugin --skill evaluate-skillgit clone --depth 1 https://github.com/8090-inc/software-factory-pluginWrote 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/8090-inc/software-factory-plugin/evaluate-skill)<a href="https://agentmods.dev/skills/8090-inc/software-factory-plugin/evaluate-skill"><img src="https://agentmods.dev/badge/skills/8090-inc/software-factory-plugin/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 | $0.00016 | $0.00475 |
| Opus 5 | $0.00008 | $0.00237 |
| Sonnet 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 4d 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.
This is a copy
100% identical to evaluate-skill — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
- 4d ago First seen · 52 lines · 16 tokens per session scan A a72958959a4d
evaluate-skill is a skill published in the GitHub repository 8090-inc/software-factory-plugin (7 stars, last pushed 2mo ago), licensed MIT. It adds 16 tokens to every session and 475 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to evaluate-skill, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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.
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…