backend

A default instruction template for a backend role in the M14 agent setup.

In plain words
What is it for?
It helps initialize or update the backend role for a project.
Why use it?
It gives the role a starting point while preserving edits made outside the managed section.

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/claude-genasis/genasis/backend
Clone the repo
git clone --depth 1 https://github.com/claude-genasis/genasis

Made for: Claude Code.

Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 115 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 86% 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.00008 $0.00115
Opus 5 $0.00004 $0.00057
Sonnet 5 $0.00002 $0.00023
Haiku 4.5 $0.00001 $0.00012

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

Security

Grade A, and why

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

86% identical to architect — 12 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.

tests/golden/blank/expected/.claude/agents/backend.md · 17 lines

What it actually says

backend overlay

project: blank-fixture

backend

Default base body for the backend role. The marker fence below this line is owned by Genasis (attach/upgrade rewrites it). Anything outside the fence is yours to edit.

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 · 17 lines · 8 tokens per session scan A 806bcf1ac625

Subscribe to this mod's changes

backend is an agent published in the GitHub repository claude-genasis/genasis (7 stars, last pushed 3mo ago), licensed MIT. It adds 8 tokens to every session and 115 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to architect, differing in 12 lines, and is treated as a copy.

Related

Other agents, from other repositories

adapter

Thirteen coding agents report to RimZ, and no code outside crates/rimz/src/agents/ knows which one it is looking at. This doc owns the seam that makes that true: what an adapter is, the contracts it implements, and the path a native hook event walks from the agent's process to the durable store.

rimio-ai/rimz · 0 tokens

adapter_copilot

GitHub Copilot CLI reports through native camelCase command hooks installed as one RimZ-owned user file at $COPILOTHOME/hooks/rimz.json, falling back to /.copilot/hooks/rimz.json. Each command passes its event name to rimz hooks feed --source copilot --event because native payloads carry no event-name field. Hook…

rimio-ai/rimz · 0 tokens

adapter_opencode

This doc is the single home for everything OpenCode-specific. OpenCode's integration surface is an in-process TypeScript plugin, so the adapter ships plugin.ts, embedded at compile time and installed as /.config/opencode/plugin/rimz.ts. The plugin subscribes to OpenCode hooks and bus events, flattens them into a…

rimio-ai/rimz · 0 tokens

planner

Use after the structure is produced to create the tactical implementation plan. Translates each vertical slice in structure.md into precise file-level steps with acceptance test mappings. The plan is a tactical artifact for the implementer — neither the structure nor the plan is human-reviewed (the design passed…

bostonaholic/team · 61 tokens

adapter_amp

Amp exposes no command-hook, statusline, or interactive RPC protocol, so RimZ owns the wire: plugin.ts is installed at /.config/amp/plugins/rimz.ts and forwards observation-only envelopes to rimz hooks feed --source amp. Upstream drift in that envelope is a RimZ adapter bug.

rimio-ai/rimz · 0 tokens

AGENTS

Local contract for crates/rimz/src/agents/ — the integration layer. Extends crates/rimz/AGENTS.md.

rimio-ai/rimz · 0 tokens