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/featurenpx skills add MichiBl/Claude-Code-Default-Repo --skill featuregit 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/feature)<a href="https://agentmods.dev/skills/michibl/claude-code-default-repo/feature"><img src="https://agentmods.dev/badge/skills/michibl/claude-code-default-repo/feature.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.02345 |
| Opus 5 | $0.00049 | $0.01172 |
| Sonnet 5 | $0.00020 | $0.00469 |
| Haiku 4.5 | $0.00010 | $0.00234 |
Grade A, and why
feature 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.
How it starts
The opening of the file, as written. The whole thing — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/feature — Agent-Team-Pipeline
Du steuerst als Haupt-Agent ein Feature durch eine strikte, sequentielle Pipeline mit Bestätigungs-Gates. Subagenten liefern Spezifikation, Plan, Review und QA — die Implementierung machst du selbst und delegierst sie nicht (du hast den vollen Konversationskontext; jedes Handoff kostet Kontext).
Wann nutzen / wann nicht
Nutzen: neues Feature, neue Integration, Refactor über mehrere Dateien, alles was Schema + Backend + UI zugleich berührt, oder wenn der User es explizit verlangt.
Nicht nutzen: Typo oder Einzeiler-Fix (direkt fixen), Bugfix oder
kleines Refactoring mit klarem Ziel (-> /fix), reines
Dependency-Update, fehlender Test für bereits gebauten Code (qa-engineer
direkt aufrufen), Exploration/Q&A (direkt beantworten).
Preconditions (Hard-Stop)
Prüfe vor dem Start beide Voraussetzungen; fehlt eine, stoppe sofort und bootstrappe sie NIE als Nebenprodukt eines Feature-Laufs:
-
Test-Infrastruktur — die QA-Phase schreibt und führt echte Tests aus. Es braucht einen konfigurierten Test-Runner UND mindestens eine Testdatei im Repo. Fehlt sie, frage den User:
"Die /feature-Pipeline braucht funktionierende Test-Infrastruktur. Soll ich die zuerst mit
/bootstrapaufsetzen (eigene Aufgabe), bevor wir das Feature starten?" -
Lint-Gate — verify.sh, CI und QA linten nur, was existiert. Es braucht einen eingerichteten Linter (Node:
lint-Script inpackage.json; Python: ruff in den Dev-Dependencies; andere Stacks:.claude/hooks/verify-project.shvorhanden). Fehlt er, frage den User:"Das Projekt hat kein Lint-Gate — verify.sh, CI und QA würden ohne Linter laufen. Soll ich zuerst mit
/bootstrapeinen einrichten (eigene Aufgabe)?"
Slug-Ableitung
Leite aus dem User-Argument einen kebab-case-<slug> ab (Kleinbuchstaben,
Bindestriche, keine Sonderzeichen). Alle Artefakte leben unter
docs/features/<slug>/. Nenne den Slug dem User zu Beginn; bei Unklarheit
per AskUserQuestion klären.
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 · 183 lines · 98 tokens per session scan A 5654cf91ff34
feature 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 2,345 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…