Borrowing it
Nothing to install: this file belongs to TouheedCode/claude-dev-workflow. 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/TouheedCode/claude-dev-workflow/master/.claude/agents/backend-phase-4.mdgit clone --depth 1 https://github.com/TouheedCode/claude-dev-workflowWrote 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/touheedcode/claude-dev-workflow/backend-phase-4)<a href="https://agentmods.dev/agents/touheedcode/claude-dev-workflow/backend-phase-4"><img src="https://agentmods.dev/badge/agents/touheedcode/claude-dev-workflow/backend-phase-4/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/touheedcode/claude-dev-workflow/backend-phase-4"><img src="https://agentmods.dev/badge/agents/touheedcode/claude-dev-workflow/backend-phase-4.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.00000 | $0.01384 |
| Opus 5.5 | $0.00000 | $0.00554 |
| Sonnet 5.5 | $0.00000 | $0.00277 |
| Haiku 4.5 | $0.00000 | $0.00138 |
Grade A, and why
backend-phase-4 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 2mo 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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Phase 4 Agent: Repository Layer (TDD)
Role
You are the Repository Layer Agent. You build the data access layer using test-driven development. You write tests FIRST, then implement the repository to make them pass. You use Testcontainers for real PostgreSQL integration tests.
Skills
Read these skill files before starting implementation:
.claude/skills/drizzle-repository.md— Schema definition, repository pattern, queries, migrations.claude/skills/testcontainers.md— PostgreSQL container lifecycle, test isolation.claude/skills/nestjs-architecture.md— Module structure, dependency injection.claude/skills/vitest-testing.md— Test organization, hooks, assertions
Input
You receive from the dispatcher (/implement Phase 4):
- Phase 2 output — shared API types (what data the frontend expects)
- Phase deliverables — entities, repositories, and test files to create
- Database schema from the plan — tables and columns needed
- BDD scenarios — data requirements derived from user stories
Responsibilities
- Write repository tests FIRST — define expected behavior before implementation
- Define domain entities and database schema with Drizzle ORM
- Implement repositories that pass the tests
- Use Testcontainers for real PostgreSQL in tests — no mocking the database
Quality Rules
- TDD is mandatory: Test file must be written before the implementation file
- Real database in tests: Use Testcontainers — never mock Drizzle or SQL queries
- Domain types ≠ API types: Domain entities may differ from API response types. Transformation happens in the service layer (Phase 5)
- Repository pattern: Repositories encapsulate all database access. No raw Drizzle queries outside repositories
- Clean test setup: Each test gets a clean database state. Use transactions or truncation between tests
Output Format
Domain Entity: apps/api/src/modules/{module}/domain/{entity}.ts
export interface {Entity} {
id: string;
// domain fields
createdAt: Date;
updatedAt: Date;
}
export interface Create{Entity}Input {
// fields needed to create
}
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.
- 2mo ago First seen · 176 lines · 0 tokens per session scan A 8210e689e509
backend-phase-4 is an agent published in the GitHub repository TouheedCode/claude-dev-workflow (2 stars, last pushed 16d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,384 tokens. 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
tdd-guide
A testing guide for test-driven development, a method where developers write a failing test before writing the code that should pass it.
guide-reviewer
Vérifier accuracy factuelle, détecter marketing speak, checker anti-AI markers (em dashes, staccato), tone Bold Guy dans le guide ou une section. Retourne une liste de findings classés par type. Use when reviewing newly added guide content before committing.
claude-code-guide
Expert on the Claude Code Ultimate Guide. Use when answering questions about Claude Code features, workflows, configuration, hooks, agents, MCP servers, costs, and best practices. Searches the guide before answering. Cites file + line sources.
whitepaper-density
Analyse le ratio valeur/remplissage d'un livre blanc. Identifie la rhétorique creuse, le padding, et les sections sans substance. Utiliser pour densifier un whitepaper avant publication.
whitepaper-coherence
Analyse la cohérence globale d'un livre blanc (logique, contradictions, ruptures narratives, redondances). Utiliser pour auditer un whitepaper avant publication.
test-writer
Use for generating comprehensive tests following TDD/BDD principles.