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/michibl/claude-code-default-repo/fixnpx skills add MichiBl/Claude-Code-Default-Repo --skill fixgit clone --depth 1 https://github.com/MichiBl/Claude-Code-Default-RepoWrote 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/michibl/claude-code-default-repo/fix)<a href="https://agentmods.dev/skills/michibl/claude-code-default-repo/fix"><img src="https://agentmods.dev/badge/skills/michibl/claude-code-default-repo/fix.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.1 | $0.00098 | $0.00636 |
| Opus 5 | $0.00049 | $0.00318 |
| Sonnet 5 | $0.00020 | $0.00127 |
| Haiku 4.5 | $0.00010 | $0.00064 |
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 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
/fix — Fast Lane für kleine Änderungen
Du behebst eine klar umrissene Änderung direkt — ohne Requirements-Gate,
ohne Architektur-Gate, ohne Subagenten. Die Qualitätssicherung übernimmt der
Stop-Hook (.claude/hooks/verify.sh): Er lintet und testet automatisch am
Ende jeder Antwort. Baue keine eigenen Gates nach.
Wann nutzen / wann nicht
Nutzen: Bugfix mit klarer Symptombeschreibung, kleines Refactoring (1–3 Dateien), Doku-Update, Konfigurations-Korrektur.
Nicht nutzen: neues Feature, Refactor über viele Dateien, alles was
Schema + Backend + UI zugleich berührt (-> /feature), reine Fragen
(direkt beantworten). Reiner Typo/Einzeiler: einfach fixen, dieser Workflow
wäre schon Overhead.
Workflow
- Ursache statt Symptom. Lokalisiere die tatsächliche Ursache (Lesen/Grep, ggf. Reproduktion). Fixe nie nur die Stelle, an der der Fehler sichtbar wird, wenn die Ursache woanders liegt.
- Regressionstest zuerst (bei Bugs). Schreibe einen Test, der den Bug reproduziert und rot ist. Ausnahmen: keine Test-Infrastruktur vorhanden oder nicht sinnvoll testbar (z. B. Doku, Kommentar, Config) — dann in einem Satz begründen, warum kein Test.
- Minimale Änderung. Setze den kleinsten Fix um, der die Ursache
behebt und den Test grün macht. Respektiere Konventionen und harte
Grenzen aus
CLAUDE.md. Keine Gelegenheits-Refactorings im selben Fix. - Verifikation läuft automatisch.
verify.sh(Stop-Hook) führt Lint/Typecheck/Tests aus und blockt, bis alles grün ist — nicht manuell duplizieren. - Commit. Conventional Commit (
fix:/docs:/chore:/refactor:). Kein Artefakt unterdocs/features/— das ist der Pipeline vorbehalten.
Eskalation
Stellt sich mittendrin heraus, dass die Änderung größer ist als gedacht
(neue Dependencies, Schema-Änderung, > ~3 Dateien Produktivcode, unklare
Anforderungen): stoppe, sag dem User warum, und schlage /feature vor.
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 · 47 lines · 98 tokens per session scan A bbfe69fb8751
fix is a skill published in the GitHub repository MichiBl/Claude-Code-Default-Repo (2 stars, last pushed 15d ago), licensed MIT. It adds 98 tokens to every session and 636 once invoked, about $0.0005 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…
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…