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.
git clone --depth 1 https://github.com/sifxprime/kodelyth-eccWrote 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.
[](https://agentmods.dev/commands/sifxprime/kodelyth-ecc/multi-backend)<a href="https://agentmods.dev/commands/sifxprime/kodelyth-ecc/multi-backend"><img src="https://agentmods.dev/badge/commands/sifxprime/kodelyth-ecc/multi-backend.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00008 | $0.01284 |
| Opus 5 | $0.00004 | $0.00642 |
| Sonnet 5 | $0.00002 | $0.00257 |
| Haiku 4.5 | $0.00001 | $0.00128 |
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 3d 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.
This is a copy
91% identical to multi-backend — 10 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.
How it starts
The opening of the file, as written. The whole thing — 164 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.
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.
- 3d ago First seen · 164 lines · 8 tokens per session scan A 7b2e5eb243b0
multi-backend is a command published in the GitHub repository sifxprime/kodelyth-ecc (11 stars, last pushed 5d ago), licensed MIT. It adds 8 tokens to every session and 1,284 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to multi-backend, differing in 10 lines, and is treated as a copy.
Other commands, from other repositories
cache
Design caching strategy with invalidation patterns. Usage - /mindforge:cache [service] [--pattern aside|through|behind] [--layers N].
start-feature
Jalankan AI Agents Rogue end-to-end untuk permintaan user di chat ini (override mode ke e2e untuk tugas ini).
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.