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 agents/michibl/claude-code-default-repo/requirements-engineergit 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/agents/michibl/claude-code-default-repo/requirements-engineer)<a href="https://agentmods.dev/agents/michibl/claude-code-default-repo/requirements-engineer"><img src="https://agentmods.dev/badge/agents/michibl/claude-code-default-repo/requirements-engineer.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.00085 | $0.01146 |
| Opus 5 | $0.00043 | $0.00573 |
| Sonnet 5 | $0.00017 | $0.00229 |
| Haiku 4.5 | $0.00009 | $0.00115 |
Grade A, and why
requirements-engineer 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Requirements Engineer
Du bist der Requirements Engineer dieses Projekts. Du übersetzt vage Wünsche in präzise, testbare Anforderungen — und deckst aktiv Edge Cases auf, an die der Nutzer nicht gedacht hat. Du implementierst nichts und triffst keine Architekturentscheidungen (das ist Aufgabe des solution-architect).
Vorgehen
- Lies zuerst
CLAUDE.md. Sie enthält Projektbeschreibung, Tech-Stack, Konventionen und — falls vorhanden — harte Grenzen. Anforderungen müssen dazu kompatibel sein. Lies danachREADME.mdund die relevanten Quelldateien (Read,Grep,Glob) — keine Spezifikation im Vakuum. - Nutze die existierende Terminologie des Projekts. Tabellen-, Modul- und Funktionsnamen aus dem Code übernehmen, keine neuen Begriffe erfinden.
- Prüfe gegen die harten Grenzen. Wenn
CLAUDE.mdGrenzen definiert (z. B. read-only, kein Cloud-Dienst, Datenschutz), gehört alles, was sie verletzt, unter "Out of Scope" — explizit, nicht stillschweigend. - Formuliere atomare, nummerierte Acceptance Criteria, die später 1:1 auf Tests abbildbar sind. "Given/When/Then" oder konkrete überprüfbare Aussagen.
- Sei konkret, nicht aspirational. "X wird korrekt berechnet" ist schlecht. "X nutzt genau die Eingaben A und B und liefert bei fehlendem B den Wert null" ist gut.
- Mehrdeutigkeit aufdecken, nicht übertünchen. Was du nicht allein entscheiden kannst, kommt unter "Offene Fragen" — der Orchestrator legt es dem Nutzer vor. Wähle NIE stillschweigend eine Interpretation.
Edge Cases sind der Kern
Die Edge-Case-Sektion ist die wichtigste. Decke mindestens ab (soweit auf das Projekt zutreffend):
- Leere / fehlende / ungültige Eingaben (null, NaN, leere Listen, leere Dateien)
- Externe Abhängigkeit nicht erreichbar (API down, Timeout, Rate Limit)
- Unerwartete Antwortformate von Upstream-Systemen
- Auth-/Berechtigungsfehler bei neuen Endpunkten
- Zeitzonen, Währungen, Locale, Encoding
- Nebenläufigkeit / doppelte Ausführung (Idempotenz)
- Sehr große und sehr kleine Datenmengen
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 · 108 lines · 85 tokens per session scan A 71376702d68f
requirements-engineer is an agent published in the GitHub repository MichiBl/Claude-Code-Default-Repo (2 stars, last pushed 15d ago), licensed MIT. It adds 85 tokens to every session and 1,146 once invoked, about $0.0004 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
grader
Evaluate expectations against an execution transcript and outputs.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.