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/trojava/spec-driven-dev-kit/feature-umsetzennpx skills add trojava/spec-driven-dev-kit --skill feature-umsetzengit clone --depth 1 https://github.com/trojava/spec-driven-dev-kitWhat 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 | $0.00052 | $0.00448 |
| Opus 5 | $0.00026 | $0.00224 |
| Sonnet 5 | $0.00010 | $0.00090 |
| Haiku 4.5 | $0.00005 | $0.00045 |
Grade A, and why
feature-umsetzen 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 yesterday.
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
Feature umsetzen
Voraussetzungen
- Lies
AGENTS.md, die Projektdokumente und alle Dateien des Feature-Ordners. - Prüfe, dass Spezifikation und Plan freigegeben sind.
- Beginne nur, wenn der Benutzer die Umsetzung ausdrücklich beauftragt hat.
- Bearbeite die ausdrücklich genannte Aufgabe. Falls keine Aufgabe genannt ist, frage nach und ändere keinen Code.
Aufgabe bearbeiten
- Prüfe Bezug, Ergebnis und vorgesehene Prüfung der Aufgabe.
- Untersuche den betroffenen Code und bestehende Tests.
- Implementiere nur den erforderlichen Umfang.
- Ergänze oder aktualisiere Tests und notwendige Dokumentation.
- Führe zuerst die aufgabenspezifische Prüfung und danach angemessene Regressionstests aus.
- Markiere die Aufgabe nur bei erfolgreicher Prüfung mit
[x]. - Stoppe nach dieser Aufgabe. Bearbeite keine weitere Aufgabe ohne ausdrückliche Aufforderung.
Bei Abweichungen
- Stoppe bei widersprüchlichen oder nicht erfüllbaren Vorgaben.
- Behandle fachliche Anpassungswünsche an ein bereits umgesetztes Feature
zuerst mit
$feature-spezifizierenund anschließend mit$umsetzung-planen. Ändere bis zu deren Freigabe keinen Code. - Dokumentiere neu entdeckte Arbeit als zusätzliche Aufgabe.
- Verlange eine Aktualisierung und erneute Freigabe, wenn sich eine Anforderung oder ein wesentlicher Planschritt ändern muss.
- Lasse die Aufgabe offen, wenn eine Prüfung fehlschlägt oder nicht ausgeführt werden konnte.
Abschluss
Berichte:
- bearbeitete Aufgabe und Änderungen,
- ausgeführte Prüfungen mit Ergebnis,
- verbleibende Risiken, Einschränkungen oder Folgeaufgaben.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 47 lines · 52 tokens per session scan A 5492143ac5ea
feature-umsetzen is a skill published in the GitHub repository trojava/spec-driven-dev-kit (5 stars, last pushed 2mo ago), licensed MIT. It adds 52 tokens to every session and 448 once invoked, about $0.0003 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.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…