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-pruefennpx skills add trojava/spec-driven-dev-kit --skill feature-pruefengit 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.00064 | $0.00500 |
| Opus 5 | $0.00032 | $0.00250 |
| Sonnet 5 | $0.00013 | $0.00100 |
| Haiku 4.5 | $0.00006 | $0.00050 |
Grade A, and why
feature-pruefen 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 prüfen
Prüfumfang bestimmen
Lies AGENTS.md, die Projektdokumente und alle Dateien des Feature-Ordners.
Prüfe je nach Entwicklungsstand nur die vorhandenen Artefakte:
- Vor Umsetzung: Spezifikation, Plan und Aufgabenliste.
- Nach Umsetzung: zusätzlich Codeänderungen, Tests und Dokumentation.
Ändere bei einer Prüfung keine Dateien, außer der Benutzer fordert Korrekturen ausdrücklich an.
Artefakte prüfen
- Suche unklare, widersprüchliche oder nicht überprüfbare Anforderungen.
- Prüfe Normal-, Fehler- und Randfälle sowie relevante nichtfunktionale Anforderungen.
- Prüfe die Verknüpfung
Anforderung → Planschritt → Aufgabe → Prüfung. - Suche unbegründete technische Entscheidungen, fehlende Risiken, Abhängigkeiten und Rücknahmemöglichkeiten.
- Prüfe, ob Aufgaben angemessen geschnitten, geordnet und einzeln prüfbar sind.
- Kennzeichne unnötige Wiederholungen, übermäßig kleinteilige Anforderungen oder Aufgaben und Details ohne erkennbaren Nutzen für Umsetzung oder Review.
Umsetzung prüfen
- Vergleiche das beobachtbare Verhalten mit jedem Akzeptanzkriterium.
- Prüfe, ob die Implementierung den freigegebenen Umfang überschreitet.
- Untersuche Fehlerbehandlung, Sicherheit, Datenschutz und Rückwärtskompatibilität entsprechend dem Plan.
- Führe die vorgesehenen Tests aus und bewerte relevante Testlücken.
- Prüfe, ob Aufgabenstatus und Dokumentation dem tatsächlichen Stand entsprechen.
Bericht
Führe Befunde zuerst auf, nach Schweregrad geordnet. Nenne jeweils die betroffene Datei und konkrete Stelle sowie die Auswirkung. Schließe mit:
- offenen Fragen oder Annahmen,
- ausgeführten und nicht ausführbaren Prüfungen,
- einer klaren Aussage:
freigabefähigodernicht freigabefähig.
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 · 51 lines · 64 tokens per session scan A 07d2e5f8220e
feature-pruefen is a skill published in the GitHub repository trojava/spec-driven-dev-kit (5 stars, last pushed 2mo ago), licensed MIT. It adds 64 tokens to every session and 500 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…