fix

A command for fixing a small, clearly defined software bug.

In plain words
What is it for?
It helps create a tracked work folder, apply the smallest suitable code change, and validate the fix.
Why use it?
It keeps the change limited to the stated problem and requires the result to be checked.

Command

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 commands/nbpadilha/nbp-skillforge/fix
Clone the repo
git clone --depth 1 https://github.com/nbpadilha/nbp-skillforge
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 132 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.00011 $0.00132
Opus 5 $0.00005 $0.00066
Sonnet 5 $0.00002 $0.00026
Haiku 4.5 $0.00001 $0.00013

Measured 3d ago against content hash 4effb414522a, 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 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.

examples/commands/fix.md · 21 lines

What it actually says

Fix

Fix the bug with a small scope.

Working folder

At the start, create this run's folder:

RUN_DIR=$(run-dir fix "$DESC" --prefix fix --track)

The logic (slug, timestamp, tracking) lives in the script — the skill does not restate it.

Apply the minimal change and validate.

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. 3d ago First seen · 21 lines · 11 tokens per session scan A 4effb414522a

Subscribe to this mod's changes

fix is a command published in the GitHub repository nbpadilha/nbp-skillforge (8 stars, last pushed 1mo ago), licensed MIT. It adds 11 tokens to every session and 132 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-31.