fix

A guarded procedure for applying a code fix after a recent investigation has identified the problem. A worktree is a separate working copy of a Git repository, and this procedure checks that the fix is not being made directly on the default branch.

In plain words
What is it for?
Use it to implement a documented investigation result, with checks for the repository state, investigation notes, plan, tests, and related task files.
Why use it?
It prevents unsupported fixes and reduces the risk of different coding sessions overwriting each other’s branch or checkout.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/firatcand/forge/fix
Any agent
npx skills add firatcand/forge --skill fix
Clone the repo
git clone --depth 1 https://github.com/firatcand/forge

Made for: Claude Code, Codex.

Per session 20 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 478 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00020 $0.00478
Opus 5 $0.00010 $0.00239
Sonnet 5 $0.00004 $0.00096
Haiku 4.5 $0.00002 $0.00048

Measured 2d ago against content hash e91facf336d1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

fix 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 2d 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.

skills/fix/SKILL.md · 49 lines

What it actually says

/fix

Preflight: worktree guard

Task-scoped mutating skill — must run from a worktree, not the main checkout. Contract: skills/_shared/worktree-guard.md.

TOPLEVEL="$(git rev-parse --show-toplevel 2>/dev/null || echo '')"
if [ -z "$TOPLEVEL" ]; then
  echo "✗ worktree-guard: not inside a git repository" >&2
  exit 1
fi
BRANCH="$(git branch --show-current 2>/dev/null || echo '')"
DEFAULT_BRANCH="$(git symbolic-ref --short refs/remotes/origin/HEAD 2>/dev/null | sed 's@^origin/@@' || echo 'main')"
if [ -f "$TOPLEVEL/.forge/worktree-task.json" ]; then
  echo "✓ worktree-guard: $TOPLEVEL ($BRANCH)"
elif [ "$BRANCH" = "${DEFAULT_BRANCH:-main}" ]; then
  echo "✗ worktree-guard: refusing to run on default branch '$BRANCH' from $TOPLEVEL" >&2
  echo "  Parallel Claude Code sessions on the main checkout clobber each other's HEAD." >&2
  echo "  → cd into an existing worktree, or run /pickup-task to create one." >&2
  exit 1
else
  echo "⚠ worktree-guard: no .forge/worktree-task.json at $TOPLEVEL (branch: $BRANCH)" >&2
  echo "  Proceeding, but this worktree may be manually-created or stale." >&2
fi

Preconditions

plans/tasks/{LINEAR-ID}.investigation.md must exist and be < 24 hours old.

Process

  1. Read investigation
  2. Apply minimal fix matching root cause
  3. Add regression test that reproduces the original bug (Test-or-die)
  4. Verify fix + test passes
  5. Commit with conventional message: fix(scope): brief description

After 3 failed attempts

Stop. Demand fresh /investigate. Do not thrash.

Changes

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.

  1. 2d ago First seen · 49 lines · 20 tokens per session scan A e91facf336d1

Subscribe to this mod's changes

fix is a skill published in the GitHub repository firatcand/forge (13 stars, last pushed 1mo ago), licensed MIT. It adds 20 tokens to every session and 478 once invoked, about $0.0001 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.