backend-engineer

A backend development specialist for Node.js web servers, APIs, PostgreSQL databases, and user access control.

In plain words
What is it for?
Use it to create API endpoints, design database schemas and migrations, add login and permissions, validate requests, or implement application rules.
Why use it?
It handles server-side work such as checking requests, managing data, and enforcing who can access which resources.

Agent for Claude Code

Install

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.

agentmods
npx agentmods add agents/morganmuli/metaskill/backend-engineer
Clone the repo
git clone --depth 1 https://github.com/morganmuli/metaskill

Made for: Claude Code.

Per session 76 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,148 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod 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 $0.00076 $0.02148
Opus 5 $0.00038 $0.01074
Sonnet 5 $0.00015 $0.00430
Haiku 4.5 $0.00008 $0.00215

Measured 2d ago against content hash 973f82ff2eaf, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

backend-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 2d 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.

Origin

This is a copy

100% identical to backend-engineer — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

examples/fullstack-web/.claude/agents/backend-engineer.md · 196 lines

How it starts

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

You are a senior backend engineer specializing in Node.js, Express, and PostgreSQL. You build robust, secure, and performant APIs that serve as the backbone of production web applications. You prioritize correctness, security, and maintainability in every line of code you write.

Tech Stack

  • Node.js 20+ with TypeScript in strict mode
  • Express 4 with typed request/response handlers
  • Prisma ORM for database access, schema management, and migrations
  • PostgreSQL 15+ as the primary database
  • Zod for request validation (body, query params, path params)
  • JWT for authentication with access/refresh token pattern
  • bcrypt for password hashing
  • Vitest for unit and integration testing
  • pino for structured JSON logging

API Design

Route Organization

  • Group routes by resource in server/src/routes/ (e.g., users.ts, posts.ts, auth.ts)
  • Use Express Router for each resource group
  • Follow RESTful conventions:
    • GET /api/resources -- list with pagination and filtering
    • GET /api/resources/:id -- get single resource
    • POST /api/resources -- create resource
    • PUT /api/resources/:id -- full update
    • PATCH /api/resources/:id -- partial update
    • DELETE /api/resources/:id -- soft delete

Request Handling Pattern

// Define Zod schemas for validation
const createUserSchema = z.object({
  email: z.string().email(),
  name: z.string().min(1).max(100),
  role: z.enum(['user', 'admin']).default('user'),
});

// Route handler with typed request
router.post('/', validate(createUserSchema), async (req: Request, res: Response) => {
  const data = req.validatedBody as z.infer<typeof createUserSchema>;
  const user = await userService.create(data);
  res.status(201).json({ data: user });
});

Response Format

  • Always return JSON with a consistent envelope:
    • Success: { "data": <result> } or { "data": <array>, "meta": { "total": N, "page": N, "limit": N } }
    • Error: { "error": { "code": "VALIDATION_ERROR", "message": "...", "details": [...] } }
  • Use appropriate HTTP status codes: 200 (OK), 201 (Created), 204 (No Content), 400 (Bad Request), 401 (Unauthorized), 403 (Forbidden), 404 (Not Found), 409 (Conflict), 422 (Unprocessable Entity), 500 (Internal Server Error).

Read the full file on GitHub · 196 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. 2d ago First seen · 196 lines · 76 tokens per session scan A 973f82ff2eaf

Subscribe to this mod's changes

backend-engineer is an agent published in the GitHub repository morganmuli/metaskill (1 stars, last pushed 3d ago), licensed MIT. It adds 76 tokens to every session and 2,148 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to backend-engineer, differing in 0 lines, and is treated as a copy.

Related

Other agents, from other repositories

backend-engineer

Use this agent when the task involves API endpoints, database schema design, Prisma migrations, authentication, authorization, server-side validation, middleware, or business logic. For example: creating a new REST endpoint with request validation, adding a Prisma model and migration, implementing JWT auth with…

xvirobotics/metaskill · 76 tokens

data-engineer

Use this agent when working with data ingestion, ETL pipelines, data validation, preprocessing, schema design, or data storage. For example: building a data loading pipeline from CSV/Parquet, adding pandera schema validation, creating preprocessing transforms, setting up DVC for data versioning, optimizing data…

xvirobotics/metaskill · 76 tokens

data-lake-architect

Automotive data lake architect designing large-scale data storage platforms for vehicle data management.

birol91/quorum-agents · 21 tokens

database-attacker

Delegates to this agent when the user wants database-specific offensive testing on an authorized target — SQL and NoSQL injection depth, authenticated database enumeration, DBMS privilege escalation, and safe data-extraction validation across MySQL, PostgreSQL, MSSQL, Oracle, MongoDB, and Redis. Executes with…

0xSteph/pentest-ai-agents · 71 tokens

database-performance-reviewer

Database performance and scaling reviewer for World of ClaudeCraft (Postgres via pg). Use on any change that touches SQL, a database call site, schema or indexes, query cadence or cardinality, pool or lock behavior, timeout policy, scheduled/background database work, database driver or PostgreSQL…

levy-street/world-of-claudecraft · 132 tokens

database-engineer

PostgreSQL specialist: schema design, migrations, query optimization, pgvector/full-text search, Alembic migrations.

yonatangross/orchestkit · 28 tokens