Borrowing it
Nothing to install: this file belongs to MichiBl/Claude-Code-Default-Repo. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/MichiBl/Claude-Code-Default-Repo/main/.claude/agents/requirements-engineer.mdgit 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/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<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="Reviewed on agentmods" width="80" 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.01428 |
| Opus 5.5 | $0.00034 | $0.00571 |
| Sonnet 5.5 | $0.00017 | $0.00286 |
| Haiku 4.5 | $0.00009 | $0.00143 |
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 16d 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 — 127 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.
- Roadmap-AK übernehmen, wenn der Orchestrator welche übergibt. Jedes AK
aus
docs/requirements-status.mdlandet im Abschnitt "Roadmap-Bezug": von mindestens einem AC abgedeckt, oder als "geändert"/"nicht abgedeckt" mit Begründung und zugehörigem Eintrag unter "Offene Fragen". Präzisieren ist erwünscht; ein AK still weglassen oder umdeuten nicht — sonst fehlt nach dem Merge etwas, das auf der Roadmap als erledigt gilt.
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.
- 16d ago Changed · +4 lines 8835691b3d20
- 29d ago Changed · +15 lines 9081aefdd2eb
- 2mo 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 yesterday), licensed MIT. It adds 85 tokens to every session and 1,428 once invoked, about $0.0003 per session on Opus 5.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
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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.