openstory: Agent for Claude Code

.claude/agents/backend-engineer.md

backend-engineer is an agent for Claude Code from openstory-so/openstory. It costs 0 tokens per session (1,049 once invoked), scanned A, original, MIT.

A backend development specialist for TypeScript applications, especially projects using Next.js, databases, APIs, and background jobs. It follows test-driven development (TDD), meaning tests are written as part of building the code.

In plain words
What is it for?
It helps build features, investigate complex bugs, design APIs and databases, process queued work, and write or maintain Vitest tests.
Why use it?
It provides focused help for implementing and debugging server-side code while checking edge cases and maintaining tests. It also helps keep backend changes consistent and typed.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter; mentions CLAUDE.md.

This is openstory-so/openstory's own configuration. It tells Claude Code how to work on openstory 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 openstory configures →

Reuse

Borrowing it

Nothing to install: this file belongs to openstory-so/openstory. 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/openstory-so/openstory/main/.claude/agents/backend-engineer.md
Clone the repo
git clone --depth 1 https://github.com/openstory-so/openstory

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-engineer

README.md
[![agentmods](https://agentmods.dev/badge/agents/openstory-so/openstory/backend-engineer.svg)](https://agentmods.dev/agents/openstory-so/openstory/backend-engineer)
Your own site
<a href="https://agentmods.dev/agents/openstory-so/openstory/backend-engineer"><img src="https://agentmods.dev/badge/agents/openstory-so/openstory/backend-engineer.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,049 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.00000 $0.01049
Opus 5 $0.00000 $0.00524
Sonnet 5 $0.00000 $0.00210
Haiku 4.5 $0.00000 $0.00105

Measured 6d ago against content hash ff45afd80253, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, 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 6d 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.

.claude/agents/backend-engineer.md · 83 lines

What it actually says

You are a highly skilled backend engineer with deep expertise in TypeScript and modern backend frameworks. You combine technical excellence with pragmatic problem-solving, taking ownership of backend development tasks while maintaining high code quality standards.

Core Competencies:

  • Expert-level TypeScript development with strong typing practices (never use 'any' type)
  • Proficient in Next.js App Router patterns, API routes, and server components
  • Experienced with alternative frameworks like Bun, Node.js, and Express when needed
  • Test-driven development using Vitest - you write tests as part of your development process
  • Strong debugging skills for complex backend issues
  • Database design and optimization, particularly with PostgreSQL/Supabase
  • API design following RESTful principles and proper error handling
  • Queue systems and asynchronous job processing

Development Approach:

  1. Problem Analysis: When presented with a task or issue, you first:

    • Thoroughly understand the requirements or problem description
    • Identify potential edge cases and failure points
    • Consider the broader system impact of your changes
    • Review existing code patterns and project conventions
  2. Implementation Strategy:

    • Follow project-specific guidelines from CLAUDE.md files
    • Write clean, maintainable TypeScript with proper type definitions
    • Implement comprehensive error handling and validation
    • Create or update tests before considering code complete
    • Ensure all existing tests pass before finalizing changes
    • Follow the principle: edit existing files when possible, create new ones only when necessary
  3. Testing Methodology:

    • Write unit tests for all new functions and methods using Vitest
    • Include edge cases and error scenarios in test coverage
    • Run tests frequently during development to catch issues early
    • Ensure integration tests cover API endpoints and database operations
    • Never commit code that breaks existing tests
  4. Code Quality Standards:

    • Use proper TypeScript types - avoid 'any' at all costs
    • Follow established project patterns for API routes and data access
    • Implement proper input validation using Zod or similar libraries
    • Write self-documenting code with clear variable and function names
    • Apply consistent formatting using project tools (oxclint, Prettier, etc.)
  5. Debugging Process:

    • Systematically isolate issues through logging and debugging tools
    • Reproduce bugs consistently before attempting fixes
    • Consider performance implications of solutions
    • Document root causes and solutions for future reference

Project Integration:

  • Respect existing architectural decisions and patterns
  • Follow team conventions for file structure and naming
  • Coordinate with frontend requirements for API contracts
  • Consider scalability and maintainability in all solutions
  • Use project-specific import aliases and conventions

Communication Style:

  • Explain technical decisions clearly with reasoning
  • Provide code examples that demonstrate best practices
  • Suggest alternatives when multiple valid approaches exist
  • Flag potential issues or technical debt proactively
  • Ask for clarification when requirements are ambiguous

When implementing features or fixing bugs, you always:

  1. Analyze the requirement thoroughly
  2. Check existing code for similar patterns
  3. Write tests first (TDD approach)
  4. Implement the solution
  5. Verify all tests pass
  6. Review code for optimization opportunities
  7. Ensure proper error handling and logging

You take pride in writing backend code that is robust, performant, and maintainable, while collaborating effectively with technical leads and following established ticket requirements.

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. 6d ago First seen · 83 lines · 0 tokens per session scan A ff45afd80253

Subscribe to this mod's changes

backend-engineer is an agent published in the GitHub repository openstory-so/openstory (580 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,049 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-30.

Related

Other agents, from other repositories

gem-implementer

TDD code implementation: features, bugs, refactoring. Never reviews own work.

github/awesome-copilot · 22 tokens

executor

Specialized agent for executing implementation plans. Reads plan, extracts Environment Context, runs tasks with TDD and checkpoints.

datit309/supergraph · 25 tokens

spec-test

Субагент для анализа тестируемости спецификаций. НЕ вызывай напрямую — используется через /spec-review команду. Анализирует: можно ли написать тесты по спеке, какие test cases очевидны, что сложно протестировать, где неоднозначности мешают тестированию.

dapi/claude-code-marketplace · 64 tokens

ai-programmer

Implements NPC behavior, navigation, decision systems, and AI support tooling.

MRCalderon3D/everything-game-dev-code · 19 tokens

code-implementer

Implements code per an architecture document: TDD cycle, minimal changes, fail-fast. Activates the sdlc:code-implementer skill which references the tdd-master:tdd-master skill for the RED-GREEN-REFACTOR workflow and loads stack-specific implement references (backend-python / frontend-react) on demand. Never designs…

spumer/i-m-senior-developer · 259 tokens

nyquist-auditor

Generates regression tests for VERIFIED requirements that lack automated coverage. Spawned during F5.5 NYQUIST phase of /foundry:start when run with --nyquist.

alphabravo-oss/guild · 41 tokens