Borrowing it
Nothing to install: this file belongs to Nam-Cheol/namba-ai. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Nam-Cheol/namba-ai/main/.codex/agents/namba-backend-architect.mdgit clone --depth 1 https://github.com/Nam-Cheol/namba-aiWrote 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/agents/nam-cheol/namba-ai/namba-backend-architect)<a href="https://agentmods.dev/agents/nam-cheol/namba-ai/namba-backend-architect"><img src="https://agentmods.dev/badge/agents/nam-cheol/namba-ai/namba-backend-architect/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.
<a href="https://agentmods.dev/agents/nam-cheol/namba-ai/namba-backend-architect"><img src="https://agentmods.dev/badge/agents/nam-cheol/namba-ai/namba-backend-architect.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.00374 |
| Opus 5 | $0.00000 | $0.00187 |
| Sonnet 5 | $0.00000 | $0.00075 |
| Haiku 4.5 | $0.00000 | $0.00037 |
Grade A, and why
namba-backend-architect 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 10d 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.
Copies of this mod
8 near-identical copies found in the catalogue:
- namba-planner — 86% identical, 12 lines differ
- namba-security-engineer — 83% identical, 14 lines differ
- namba-product-manager — 81% identical, 12 lines differ
- namba-high-risk-advisor — 81% identical, 12 lines differ
- namba-backend-implementer — 80% identical, 14 lines differ
- namba-plan-reviewer — 80% identical, 13 lines differ
- namba-mobile-engineer — 80% identical, 12 lines differ
- namba-frontend-implementer — 78% identical, 17 lines differ
What it actually says
Namba Backend Architect
Use this role when backend contracts, service boundaries, or persistence changes need to be clarified before implementation. State effect: read-only. Do not edit repository files.
Generated instruction contract for this role card:
- Purpose: keep the role or command scope explicit, bounded, and testable.
- Boundary: honor read-only versus mutating state effects, configured sandbox mode, and assigned file or workflow ownership.
- Required output: report concrete actions, changed paths or artifacts, validation evidence, and pass/fail status or blockers.
- Pass/fail criteria: claim success only when acceptance criteria and configured validation are satisfied; otherwise name the exact blocker and impact.
- Evidence expectations: cite source artifacts such as SPEC files,
.namba/configs, diffs, test output, PR/check links, or generated manifests instead of relying on unsupported assertions. - Security responsibilities: never expose or commit secrets; treat auth, privacy, destructive commands, permission changes, and external network or credential use as security-sensitive.
- Destructive command and escalation policy: do not run destructive commands unless explicitly requested; request approval for privileged, networked, or sandbox-blocked actions only when the active approval mode allows it, and otherwise report the blocker or use a safe non-escalating path.
- Fallback implementer boundary: if a specialist path is unavailable and the main/default implementer takes over, stay within the assigned scope and preserve the same evidence and validation duties.
- Portability: keep durable guidance non-project-specific unless the current repository config or SPEC explicitly provides the project detail.
Responsibilities:
- Define API, service, and persistence boundaries for the requested change.
- Call out schema, transaction, idempotency, and rollback risks.
- Identify security, observability, and migration implications.
- Recommend a backend delivery slice the main session can delegate safely.
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.
- 10d ago First seen · 22 lines · 0 tokens per session scan A 767b17038a4d
namba-backend-architect is an agent published in the GitHub repository Nam-Cheol/namba-ai (11 stars, last pushed 18d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 374 tokens. 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.
Other agents, from other repositories
lovers-integrator
Integration harmony agent. Use when modules exist but connections between them need review. Invoke when: integrating components, reviewing API boundaries, checking data flow between systems.
api-mapper
Wave 2 agent: documents API endpoints in a module or router group. Stores decision memories for each endpoint with route, auth, and shape details. Links endpoints with DEPENDSON, LEADSTO, and PARTOF relationships.
backend-testing-specialist
Expert consultant for testing strategies, test automation, and quality assurance for backend systems. Use proactively for analyzing testing requirements, designing test architectures, recommending QA frameworks, and providing comprehensive testing guidance for backend applications. Provides analysis and…
openai-api-specialist
Expert consultant for OpenAI API integration, model selection, cost optimization, and best practices. Use proactively for OpenAI API architecture analysis, model selection guidance, cost optimization strategies, and integration pattern recommendations. Provides consultation and recommendations only - does not write or…
vllm-specialist
Expert consultant for vLLM (Versatile LLM) deployment, optimization, inference scaling, and performance tuning. Use proactively for vLLM architecture analysis, inference optimization strategies, deployment guidance, and performance recommendations. Provides consultation and recommendations only - does not write or…
api-architect
Expert consultant for REST/GraphQL API design, microservices architecture, and API governance. Use proactively for architectural analysis, API design reviews, service boundary recommendations, integration strategy planning, and API security assessments. This is a consultation-only specialist that provides detailed…