agentmods.dev

spec-driven-dev-kit: Agent for Claude Code

.agents/agents/backend-entwickler.md

backend-entwickler is an agent for Claude Code from trojava/spec-driven-dev-kit. It costs 67 tokens per session (728 once invoked), scanned A, original, MIT.

A backend implementation agent that builds server-side feature tasks from approved specifications, architecture decisions, plans, and API contracts. An API contract is the agreed shape and behavior of the interface used by other software.

In plain words
What is it for?
Use it to implement tagged backend tasks in a feature folder, follow the planned task order, and deliver only the API operations defined by the project's design.
Why use it?
It removes the need to manually gather the project's rules and feature documents before implementing each backend task. It also stops when required documents are not approved instead of coding against unfinished plans.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: installed under .agents/ (shared by several agents); mentions AGENTS.md.

This is trojava/spec-driven-dev-kit's own configuration. It tells Claude Code how to work on spec-driven-dev-kit itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything spec-driven-dev-kit configures →

not rated 9repo 1mo ago A scan 67 tokens original MIT
View source ↗ trojava/spec-driven-dev-kit
Reuse

Borrowing it

Nothing to install: this file belongs to trojava/spec-driven-dev-kit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/trojava/spec-driven-dev-kit/main/.agents/agents/backend-entwickler.md
Clone the repo
git clone --depth 1 https://github.com/trojava/spec-driven-dev-kit

Made for: Claude Code.

Wrote 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.

agentmods badge for backend-entwickler

README.md
[![agentmods](https://agentmods.dev/badge/agents/trojava/spec-driven-dev-kit/backend-entwickler/github.svg)](https://agentmods.dev/agents/trojava/spec-driven-dev-kit/backend-entwickler)
Your own site
<a href="https://agentmods.dev/agents/trojava/spec-driven-dev-kit/backend-entwickler"><img src="https://agentmods.dev/badge/agents/trojava/spec-driven-dev-kit/backend-entwickler/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.

agentmods 80×15 button for backend-entwickler

Your own site · 80×15
<a href="https://agentmods.dev/agents/trojava/spec-driven-dev-kit/backend-entwickler"><img src="https://agentmods.dev/badge/agents/trojava/spec-driven-dev-kit/backend-entwickler.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 67 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 728 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00067 $0.00728
Opus 5.5 $0.00027 $0.00291
Sonnet 5.5 $0.00013 $0.00146
Haiku 4.5 $0.00007 $0.00073

Measured 1mo ago against content hash b167fdd9ef16, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

backend-entwickler 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 1mo 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.

.agents/agents/backend-entwickler.md · 61 lines

How it starts

The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Rolle: Backend-Entwickler

Rolle

Du bist ein erfahrener Backend-Entwickler. Du setzt die Backend-Aufgaben eines Features eigenständig auf Basis der freigegebenen Dokumente um und lieferst die Schnittstelle exakt nach dem Vertrag unter api/.

Eingabe

Der Aufrufer nennt den Feature-Ordner unter specs/ und die Aufgaben-IDs T-xx, die du umsetzen sollst. Fehlt eine Angabe, setze alle offenen Aufgaben mit dem Tag [Backend] um.

Lies vor der Arbeit AGENTS.md, docs/prinzipien.md, docs/architektur.md, alle Dateien des Feature-Ordners und den Schnittstellenvertrag unter api/ (Datei laut A-xx), sofern das Projekt einen Vertrag hat.

Vorgehen

  1. Prüfe, dass spezifikation.md, adr.md und plan.md den Status Freigegeben haben. Andernfalls stoppe und melde den fehlenden Schritt.
  2. Arbeite die Aufgaben in der Reihenfolge aus plan.md ab. Ablauf je Aufgabe, Aufgabenstand und Anhaltegründe stehen in .agents/skills/feature-umsetzen/SKILL.md, Abschnitte Feature umsetzen, Aufgabenstand führen und Wann anhalten. Sie gelten unverändert; der Abschnitt Aufgaben verteilen gilt nicht für dich, du delegierst nicht.
  3. Setze nur die Operationen um, die die adr.md deines Features nennt, und zwar mit Typen und Fehlerverhalten genau so, wie sie im Vertrag stehen. Der Vertrag ist gegeben; du entwirfst ihn nicht neu. Verlangt eine Aufgabe eine Abweichung, halte an.
  4. Halte die Vorgaben A-xx und die Entscheidungen AD-xx ein.
  5. Schreibe zu jeder Aufgabe die vorgesehene Prüfung als automatisierten Test, soweit das möglich ist, und führe sie aus.

Grenzen

  • Ändere nur Backend-Code, Backend-Tests und Backend-Konfiguration. Bei serverseitig gerenderter Oberfläche gehören Web-Controller, die Ansichten liefern, Templates, statische Dateien und Filter für Ansichten zum Frontend; dir gehören Controller der Schnittstelle, Services und Repositories.
  • Ändere keinen Frontend-Code, keine Datei unter docs/ oder specs/ außer dem Abschnitt Aufgaben in plan.md, und keine Datei unter api/.
  • Setze keine Aufgabe ohne Tag [Backend] um.
  • Füge keine Geheimnisse zum Repository hinzu.

Read the full file on GitHub · 61 lines

Changes

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.

  1. 1mo ago First seen · 61 lines · 67 tokens per session scan A b167fdd9ef16

Subscribe to this mod's changes

backend-entwickler is an agent published in the GitHub repository trojava/spec-driven-dev-kit (9 stars, last pushed 1mo ago), licensed MIT. It adds 67 tokens to every session and 728 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-09-17.

Backend and APIs
Related

Other agents, from other repositories

php-developer

Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.

davepoon/buildwithclaude · 51 tokens

backend-reviewer

Use when reviewing service-layer logic, module boundaries, business rules, or cross-service contracts — verifies architecture integrity and service correctness against the api and architect persona standards.

jeremylongshore/tons-of-skills-marketplace · 36 tokens

integrations-engineer

Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…

avelikiy/great_cto · 106 tokens

gate

API quality gates — linting, style enforcement, breaking change CI, and API governance.

tonone-ai/tonone · 19 tokens

broadcasting-agent

Creates WebSocket broadcasting infrastructure (NestJS backend) and real-time consumption on the frontend (Next.js or React). Use when adding real-time event broadcasting to a bounded context, creating Socket.IO gateways, or implementing frontend event listeners. Dispatched after infrastructure layer is complete.

Softtor/nestjs-hexagonal · 58 tokens

dotnet-architecture-reviewer

Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…

StefanTheCode/dotnet-ai-toolkit · 102 tokens