ClaudeHack
0.000

Pin a cheaper model and fork the context in your skill frontmatter

MCP / Agents·14 hours ago·verified 14 hours ago·intermediate·~10 min setup·verified

A skill that checks a link or reformats a file does not need your session model. Set model, effort and context: fork in the frontmatter so cheap skills stay cheap.

The problem

Skills inherit the session model, effort level and full conversation context. A trivial lookup skill runs on your most expensive model and drags the entire conversation along with it.

The hack

Add `model`, `effort` and `context: fork` to a skill's frontmatter. The skill runs on the model and effort you name, in a forked subagent context that does not carry your conversation.

Why it works

The override applies only while the skill is active and is not saved to settings, so the session returns to normal on your next prompt. Forking means the skill starts clean instead of paying to re-read a long conversation it does not need.

Setup

1. Open the skill's `SKILL.md`. 2. Add `model: haiku` (or any value `/model` accepts, or `inherit`). 3. Add `effort: low` for mechanical work. 4. Add `context: fork` if the skill does not need your conversation history. 5. Invoke the skill and confirm behaviour is still correct at the lower setting. 6. Audit your other skills the same way — bias toward cheaper for anything that is lookup, formatting or validation.

Code

---
name: verify-resource
description: Check that a documentation link resolves and summarize the page in one line.
model: haiku
effort: low
context: fork
---

Fetch the URL, confirm it returns 200, and report the page title.

Additional details

Three related frontmatter fields are worth knowing at the same time: - `allowed-tools` pre-approves tools for the turn that invokes the skill, so a trusted skill does not trigger permission prompts. - `disallowed-tools` removes tools while the skill is active — the documented use case is stripping `AskUserQuestion` from a skill meant to run unattended in a background loop. - `context: fork` runs the skill in a forked subagent, which is what keeps your main context clean. The inverse is also useful: if a skill's whole job is asking you good questions, leave `AskUserQuestion` available so it presents them as a proper dialog one at a time instead of a wall of text you have to answer in prose.

Source

youtube·View original →·by Austin Marchese

Does this still work?

0 said it works · 0 said it's broken

Related

Discussion

No comments yet. Be the first to say whether this worked for you.