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/ukgovernmentbeis/inspect_evals/create-evalnpx skills add UKGovernmentBEIS/inspect_evals --skill create-evalgit clone --depth 1 https://github.com/UKGovernmentBEIS/inspect_evalsWrote 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/ukgovernmentbeis/inspect_evals/create-eval)<a href="https://agentmods.dev/skills/ukgovernmentbeis/inspect_evals/create-eval"><img src="https://agentmods.dev/badge/skills/ukgovernmentbeis/inspect_evals/create-eval.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.00046 | $0.00284 |
| Opus 5 | $0.00023 | $0.00142 |
| Sonnet 5 | $0.00009 | $0.00057 |
| Haiku 4.5 | $0.00005 | $0.00028 |
Grade A, and why
create-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 5d 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.
What it actually says
Create Evaluation
New evaluations are no longer created in the inspect_evals repository. Since May 2026, evaluations live in their own standalone repositories. This repo now serves as a register that points to upstream eval repos.
This skill has been moved to inspect-evals-template: https://github.com/Generality-Labs/inspect-evals-template/tree/main/.claude/skills/create-eval. If a user triggers this skill, inform them to go to the template to run or access the skill there.
If a user asks to create an eval, inform them that Inspect Evals no longer accepts code submissions for new evals and suggest the inspect-evals-template for guidance on creating evals.
Quick reference
| Step | Where |
|---|---|
| Create a new eval | inspect-evals-template |
| Register a completed eval | This repo — use the Prepare Evaluation For Submission skill |
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.
- 5d ago First seen · 20 lines · 46 tokens per session scan A ae770931ad6c
create-eval is a skill published in the GitHub repository UKGovernmentBEIS/inspect_evals (658 stars, last pushed yesterday), licensed MIT. It adds 46 tokens to every session and 284 once invoked, about $0.0002 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-30.
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…