multi-backend

multi-backend is a command for Claude Code from RohitBind123/claude-setup. It costs 0 tokens per session (1,209 once invoked), scanned A, a copy of multi-backend, MIT.

A command for backend development that guides work through research, idea generation, planning, implementation, optimization, and review. Backend work covers server-side APIs, algorithms, databases, and business rules.

In plain words
What is it for?
Use /backend with an API, algorithm, database, or business-logic task to organize the work from initial research through execution and review.
Why use it?
It gives server-side tasks a defined workflow and assigns different parts of the review to multiple coding models. The description says Codex leads the backend decisions while other models provide reference opinions.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: reads .claude/ paths; names the AskUserQuestion tool; mentions Codex.

Good fit Use /backend with an API, algorithm, database, or business-logic task to organize the work from initial research through execution and review.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/rohitbind123/claude-setup/multi-backend
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.

Clone the repo
git clone --depth 1 https://github.com/RohitBind123/claude-setup

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 multi-backend

README.md
[![agentmods](https://agentmods.dev/badge/commands/rohitbind123/claude-setup/multi-backend/github.svg)](https://agentmods.dev/commands/rohitbind123/claude-setup/multi-backend)
Your own site
<a href="https://agentmods.dev/commands/rohitbind123/claude-setup/multi-backend"><img src="https://agentmods.dev/badge/commands/rohitbind123/claude-setup/multi-backend/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.

agentmods 80×15 button for multi-backend

Your own site · 80×15
<a href="https://agentmods.dev/commands/rohitbind123/claude-setup/multi-backend"><img src="https://agentmods.dev/badge/commands/rohitbind123/claude-setup/multi-backend.svg" alt="Reviewed on agentmods" width="80" 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,209 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 83% 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.1 $0.00000 $0.01209
Opus 5.5 $0.00000 $0.00484
Sonnet 5.5 $0.00000 $0.00242
Haiku 4.5 $0.00000 $0.00121

Measured 1mo ago against content hash b2ca8cf77d36, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

multi-backend 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 1mo 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

83% identical to multi-backend — 15 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.

commands/multi-backend.md · 159 lines

How it starts

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

Backend - Backend-Focused Development

Backend-focused workflow (Research → Ideation → Plan → Execute → Optimize → Review), Codex-led.

Usage

/backend <backend task description>

Context

  • Backend task: $ARGUMENTS
  • Codex-led, Gemini for auxiliary reference
  • Applicable: API design, algorithm implementation, database optimization, business logic

Your Role

You are the Backend Orchestrator, coordinating multi-model collaboration for server-side tasks (Research → Ideation → Plan → Execute → Optimize → Review).

Collaborative Models:

  • Codex – Backend logic, algorithms (Backend authority, trustworthy)
  • Gemini – Frontend perspective (Backend opinions for reference only)
  • Claude (self) – Orchestration, planning, execution, delivery

Multi-Model Call Specification

Call Syntax:

# New session call
Bash({
  command: "~/.claude/bin/codeagent-wrapper {{LITE_MODE_FLAG}}--backend codex - \"$PWD\" <<'EOF'
ROLE_FILE: <role prompt path>
<TASK>
Requirement: <enhanced requirement (or $ARGUMENTS if not enhanced)>
Context: <project context and analysis from previous phases>
</TASK>
OUTPUT: Expected output format
EOF",
  run_in_background: false,
  timeout: 3600000,
  description: "Brief description"
})

# Resume session call
Bash({
  command: "~/.claude/bin/codeagent-wrapper {{LITE_MODE_FLAG}}--backend codex resume <SESSION_ID> - \"$PWD\" <<'EOF'
ROLE_FILE: <role prompt path>
<TASK>
Requirement: <enhanced requirement (or $ARGUMENTS if not enhanced)>
Context: <project context and analysis from previous phases>
</TASK>
OUTPUT: Expected output format
EOF",
  run_in_background: false,
  timeout: 3600000,
  description: "Brief description"
})

Role Prompts:

Phase Codex
Analysis ~/.claude/.ccg/prompts/codex/analyzer.md
Planning ~/.claude/.ccg/prompts/codex/architect.md
Review ~/.claude/.ccg/prompts/codex/reviewer.md

Session Reuse: Each call returns SESSION_ID: xxx, use resume xxx for subsequent phases. Save CODEX_SESSION in Phase 2, use resume in Phases 3 and 5.

Read the full file on GitHub · 159 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. 1mo ago First seen · 159 lines · 0 tokens per session scan A b2ca8cf77d36

Subscribe to this mod's changes

multi-backend is a command published in the GitHub repository RohitBind123/claude-setup (2 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,209 tokens. A static security scan graded it A with 0 findings. It is 83% identical to multi-backend, differing in 15 lines, and is treated as a copy.