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 Darwin-Agent/Car-bench-TRACE --skill climate-fan-speedgit clone --depth 1 https://github.com/Darwin-Agent/Car-bench-TRACEWrote 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/darwin-agent/car-bench-trace/climate-fan-speed)<a href="https://agentmods.dev/skills/darwin-agent/car-bench-trace/climate-fan-speed"><img src="https://agentmods.dev/badge/skills/darwin-agent/car-bench-trace/climate-fan-speed/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/darwin-agent/car-bench-trace/climate-fan-speed"><img src="https://agentmods.dev/badge/skills/darwin-agent/car-bench-trace/climate-fan-speed.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.00173 | $0.02972 |
| Opus 5 | $0.00086 | $0.01486 |
| Sonnet 5 | $0.00035 | $0.00594 |
| Haiku 4.5 | $0.00017 | $0.00297 |
Grade A, and why
climate-fan-speed 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 10d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Set the fan speed
Set the cabin fan speed. The value may be absolute ("set the fan to "), relative with an explicit step ("turn it up by "), or a vague single-step nudge with no number ("turn it up a bit", "a notch stronger", "make it blow harder"). Sometimes the control, its level parameter, or the current-speed reading is missing. The same method handles all of these.
When this applies
"Set the fan to ", "turn the fan up by ", "increase / decrease the airflow", "fan down one notch", "turn it up a bit", "blow a bit stronger". (Setting the airflow direction is climate-airflow-direction; turning AC on is climate-air-conditioning; setting the circulation mode is climate-air-circulation.) Change the fan speed only when the user's request is about the fan. When turning AC on or activating defrost is in play, do NOT pre-emptively call set_fan_speed yourself to "satisfy" a fan precondition while the control is available — that intermediate change is not what the user asked for, often gets immediately overwritten by a later explicit level, and is penalized; let the AC/defrost flow own its own fan engagement. This skill matters to those flows only when the fan-speed control is missing (then the dependent action is blocked, see below).
A bare "I'm too warm / too cold, cool me down / give me options" request that does NOT name the fan is an open comfort request, not a fan-speed change. So is a question about how to fix it — "what's the best way to improve airflow?", "can we adjust the HVAC to get more air moving?" These are exploratory questions, not calls to action: answer them, optionally offer to act, but do NOT change the fan (or any other setting) until the user explicitly picks it. Don't silently assume the fan or recite a fixed menu: read the current climate state first so the options you surface reflect reality (including any currently-active setting that could simply be eased, e.g. a running heater when the user is too warm), present the relevant levers, and only change the fan once the user actually picks it. Acting prematurely is doubly harmful here — beyond the unrequested change, it shifts the baseline a later "increase by N" reads from, so the relative change lands on the wrong target. Act on this skill alone when the user's request is specifically about the fan speed.
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.
- 10d ago First seen · 74 lines · 173 tokens per session scan A 900e505d6f93
climate-fan-speed is a skill published in the GitHub repository Darwin-Agent/Car-bench-TRACE (8 stars, last pushed 7d ago), licensed MIT. It adds 173 tokens to every session and 2,972 once invoked, about $0.0009 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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
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…