backend-dev

A backend development agent for Node.js and TypeScript services using a specified CMDO architecture, immutable data, and dependency injection. Backend services run the application logic behind a user interface or API.

In plain words
What is it for?
Use it to implement Node.js and TypeScript backend services.
Why use it?
It keeps backend implementation within the project's architecture and coding rules.

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/liorcohen/sdd/backend-dev
Clone the repo
git clone --depth 1 https://github.com/LiorCohen/sdd
Per session 27 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,526 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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.00027 $0.01526
Opus 5 $0.00014 $0.00763
Sonnet 5 $0.00005 $0.00305
Haiku 4.5 $0.00003 $0.00153

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

Security

Grade A, and why

backend-dev 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.

plugin/fullstack-typescript/agents/backend-dev.md · 153 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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 · 153 lines · 27 tokens per session scan A 25c9262c01bd

Subscribe to this mod's changes

backend-dev is an agent published in the GitHub repository LiorCohen/sdd (43 stars, last pushed 6mo ago), with no licence file. It adds 27 tokens to every session and 1,526 once invoked, about $0.0001 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.

Related

Other agents, from other repositories

chaos-monkey

You are the Chaos Monkey ("Kaos Maymunu") — a mutation-testing saboteur for the WrongStack fleet. Your job is to prove whether a test suite actually pins down the code it claims to cover, by deliberately breaking that code and watching which mutants survive.

WrongStack/WrongStack · 0 tokens

ios

You are the iOS assistant. Your job is Apple-platform app development: design and ship Swift code that compiles against the latest Apple SDKs, runs correctly on iOS/iPadOS/tvOS/watchOS/visionOS/macOS, and meets App Store and privacy requirements.

WrongStack/WrongStack · 0 tokens

explore-companion

You are the Explore Companion. Your job is to make the leader faster, not to lead. The leader is already executing the main task; you run behind it, answer one narrow probe, and hand back just enough map that the leader does not spend its own context discovering where things are.

WrongStack/WrongStack · 0 tokens

memory-curator

Agent "memory-curator" from WrongStack/WrongStack, covering core responsibilities and output.

WrongStack/WrongStack · 0 tokens

bug-hunter

You are the Bug Hunter agent. Your job is to systematically scan source code for bugs, anti-patterns, and code smells using pattern matching and heuristics. Output a prioritized hit list with file:line references.

WrongStack/WrongStack · 0 tokens

code-reviewer

You are the Code Reviewer agent. Your job is correctness-first code review of a diff or change set: find real bugs and risks, then style — and be specific.

WrongStack/WrongStack · 0 tokens