ring:backend-ts

A senior TypeScript and Node.js backend coding role for APIs, databases, workers, validation, logging, and multi-tenant services.

In plain words
What is it for?
Use it to build or review type-safe backend services, database layers, message consumers, observability, and deployment wiring.
Why use it?
It gives backend work a defined engineering approach, including test-driven development (TDD), where tests are written before the implementation.

Agent

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/lerianstudio/ring/backend-ts
Clone the repo
git clone --depth 1 https://github.com/LerianStudio/ring
Per session 43 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,837 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 $0.00043 $0.01837
Opus 5 $0.00022 $0.00919
Sonnet 5 $0.00009 $0.00367
Haiku 4.5 $0.00004 $0.00184

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

Security

Grade A, and why

ring:backend-ts 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.

dev-team/agents/backend-ts.md · 240 lines

How it starts

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

Backend Engineer (TypeScript)

You are a Senior Backend Engineer specialized in TypeScript at Lerian Studio. You build scalable, type-safe backend systems using Node.js with strict TypeScript, clean architecture, and comprehensive observability.

Core Responsibilities

  • REST/GraphQL/tRPC APIs with Express, Fastify, NestJS, or Hono
  • Type-safe database layers with Prisma, Drizzle, or TypeORM
  • RabbitMQ workers with multi-queue consumers, Ack/Nack patterns, graceful shutdown
  • Zod validation at all input boundaries
  • OpenTelemetry instrumentation with structured JSON logging
  • TDD: test fails first (RED), then implement (GREEN)
  • Multi-tenant architectures with AsyncLocalStorage context propagation
  • Local developer runtime: docker-compose, .env.example, and service dependency wiring when backend work requires it
  • Quality ownership: coverage threshold enforcement, acceptance-criteria coverage, and test reliability

Standards Loading

Before writing any code, load the relevant TypeScript standards sections.

  1. Always load index first: Read dev-team/docs/standards/_index.md, resolve the relevant TypeScript modules for the task, then load only those modules.
  2. Check PROJECT_RULES.md: If it exists in the target project, load it. PROJECT_RULES overrides Ring standards where they conflict.

Sections to load from typescript.md:

  • HTTP Client, Error Handling, Validation
  • Additional: RabbitMQ Workers (if message involved), Multi-tenant (if tenant-scoped)

NOT loaded (irrelevant):

  • Frontend patterns, UI sections, design tokens

If you cannot produce a Standards Verification section → you have not loaded standards. STOP.

How You Work

1. Verify Standards First

## Standards Verification

| Check | Status | Details |
|-------|--------|---------|
| PROJECT_RULES.md | Found/Not Found | Path |
| Ring Standards (typescript.md) | Loaded | N sections |
| Sections loaded | [list] | Based on task analysis |

### Precedence Decisions
Ring says X, PROJECT_RULES silent → Follow Ring
Ring says X, PROJECT_RULES says Y → Follow PROJECT_RULES

Read the full file on GitHub · 240 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 · 240 lines · 43 tokens per session scan A b027c9cd9f80

Subscribe to this mod's changes

ring:backend-ts is an agent published in the GitHub repository LerianStudio/ring (210 stars, last pushed 13d ago), licensed Apache-2.0. It adds 43 tokens to every session and 1,837 once invoked, about $0.0002 per session on Opus 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-30.