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/d-oit/rust-2026-template/skill-evaluatornpx skills add d-oit/rust-2026-template --skill skill-evaluatorgit clone --depth 1 https://github.com/d-oit/rust-2026-templateWhat 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.00055 | $0.01036 |
| Opus 5 | $0.00028 | $0.00518 |
| Sonnet 5 | $0.00011 | $0.00207 |
| Haiku 4.5 | $0.00006 | $0.00104 |
Grade A, and why
skill-evaluator 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 3d 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Evaluator
Evaluate local skills with a repeatable loop: inspect structure, read eval definitions, run one or more realistic prompts, then score the output with explicit assertions and evidence.
When To Use
- Test whether a skill is wired correctly
- Check whether
evals/evals.jsonexists and is usable - Run a real prompt through a skill and grade the result
- Compare a skill against a no-skill baseline or older snapshot
- Identify missing folders, weak evals, and flaky assertions
Required Inputs
At minimum, identify:
SKILL_PATH: absolute or workspace-relative path to the skill directory
GOAL: structure check / eval review / live run / baseline comparison
Evaluation Workflow
1. Structure Check
Confirm the skill directory is sane before judging outputs.
Expected layout:
skill-name/
SKILL.md
evals/evals.json # recommended
references/ # recommended
scripts/ # optional but useful
Flag these issues explicitly:
- missing
SKILL.md - nested duplicate directory like
skill-name/skill-name/ evals/exists butevals/evals.jsonis missing or invalid JSON- eval cases missing
id,prompt, orexpected_output
2. Quantitative Evaluation
Consult .agents/metrics.jsonl to assess skill performance over time.
Analyze trends in:
- Success rate
- Human intervention rate
- Token usage and duration
3. Eval Review
Read evals/evals.json if present and assess whether each case is realistic.
Good evals include:
- a real user prompt
- a short success definition
- optional input files
- assertions that are concrete and checkable
Weak evals include:
- vague prompts
- purely subjective assertions
- no evidence path for pass/fail
4. Live Run
Run at least one representative prompt from the eval set or create a focused ad hoc prompt.
For each live run:
- load the target skill
- read only the files the skill itself points to
- produce the answer or output
- grade against assertions with evidence
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 172 lines · 55 tokens per session scan A 00c17771c40a
skill-evaluator is a skill published in the GitHub repository d-oit/rust-2026-template (10 stars, last pushed 4d ago), licensed MIT. It adds 55 tokens to every session and 1,036 once invoked, about $0.0003 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
_template
Template for creating new Agentic OS skills.
skill-creator
引导用户创建和编辑符合规范的 SKILL.md 技能包。支持 DesireCore 完整格式 （frontmatter 元数据 + L0/L1/L2 分层内容 + 脚本/参考/资产）和 Claude Code 基础格式。Use when 用户要求创建新技能、更新已有技能、或将经验封装为可复用 的技能包。.
torchforge-rl-training
Provides guidance for PyTorch-native agentic RL using torchforge, Meta's library separating infra from algorithms. Use when you want clean RL abstractions, easy algorithm experimentation, or scalable training with Monarch and TorchTitan.
create-wot-ui-theme
为 wot-ui 生成单文件主题 SCSS，并在用户明确要求接入时追加 App.vue 的 @use。当用户要做品牌主题、语义变量落地、单文件主题接入时使用。.
starter-cleaner
将 wot-starter v2 模板精简为最小可开发状态，移除文档、演示分包、生成文件和 monorepo 配置，并同步清理相关 Vite 与 package.json 配置。用户要求“清理模板”“移除示例”“生成最小模板”“精简 wot-starter v2”时使用。.
wot-ui-cli
回答、使用、调试 @wot-ui/cli 时使用。关键词：wot、@wot-ui/cli、CLI、MCP、doctor、usage、lint、list、info、doc、demo、token、changelog、extract、wot mcp。适用于命令查询、参数说明、MCP 接入、本地调试、数据提取与 open-wot 仓库维护。.