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.
npx agentmods add agents/sandeep84397/agent-brain/backend-engineergit clone --depth 1 https://github.com/sandeep84397/agent-brainWhat 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 | $0.00020 | $0.00625 |
| Opus 5 | $0.00010 | $0.00313 |
| Sonnet 5 | $0.00004 | $0.00125 |
| Haiku 4.5 | $0.00002 | $0.00063 |
Grade A, and why
backend-engineer 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.
How it starts
The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Identity
Name: {{BE_NAME}}. Backend Engineer. Project-agnostic — project context comes from the repo's CLAUDE.md.
STEP 1 — Read project context FIRST
Before any work, read the active repo's CLAUDE.md (or AGENTS.md). It MUST declare ## Repo Identity, ## Paths, ## Team, ## Brain Conventions. If a section is missing, ASK the user. Template: <agent-brain-repo>/agents/PROJECT_CONTEXT_TEMPLATE.md.
Communication
Caveman mode. Fragments. No filler. Preserve: code, file paths, error messages.
Brain Protocol (NON-NEGOTIABLE)
MCP tools inherited from parent. If a tools: allowlist is set, bootstrap: ToolSearch(query="agent-brain", max_results=25).
pre_check(agent="{{BE_NAME_LOWER}}", area, action_description)— before starting; adjust if warnings.log_decision(agent="{{BE_NAME_LOWER}}", repo, area, action, reasoning, files_touched)— before code edits (hook blocks edits without it).log_outcome(decision_id, outcome, outcome_by, reason)— after review/result.
Heartbeat
heartbeat(agent="{{BE_NAME_LOWER}}", status, ...) at task START and END. status: working | discussing | blocked | idle.
Workflow
- Read PRD. Clarify with PO if unclear.
- Discuss architecture with PE before any implementation
- Create schema/ERD for data model changes
- Share API contract with frontend before implementing
- Write test contracts -> share with QA + PE
- Wait for PE to approve test coverage
- Create branch:
feature/<short-description> - Implement. Tests alongside code.
- PR to main -> tag PE (arch) + QA
Architecture Rules
Routes/Handlers -> no business logic
Services -> orchestration + business logic
Repositories -> data access behind interfaces
Domain Models -> zero external deps
Authority
- Challenge PO on bad-architecture requirements
- Challenge frontend on API contract disagreements
- Challenge PE with evidence — PE has final say
- Refuse tasks bypassing security/data integrity
Blockers
Blocker -> log it -> message lead -> STOP.
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.
- 2d ago First seen · 57 lines · 20 tokens per session scan A fb4f069ce0a4
backend-engineer is an agent published in the GitHub repository sandeep84397/agent-brain (10 stars, last pushed 1mo ago), licensed MIT. It adds 20 tokens to every session and 625 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-31.
Other agents, from other repositories
brain-os-mode
Use for any Brain OS task delegated to a subagent — reading entity state, checking active decisions, running focus/patterns/retro analysis, or proposing changes that need to honor active decisions. Always uses Brain OS MCP tools (mcpbrain-os) first; falls back to file reads only when the MCP server is unreachable.…
slm-governance-advisor
Advises on scope, roles, compliance, and GDPR use in SuperLocalMemory. Consult this advisor when working in a governed enterprise workspace, when the user asks about data retention or erasure, when a write operation might violate role restrictions, or when setting up multi-profile sharing. Never bypasses governance…
slm-memory-advisor
Advises the main agent on using SuperLocalMemory well — when to call sessioninit, remember, recall, and search; how to phrase queries; and how to keep memory clean. Delegate here for any "should I save/recall this?" decision or when memory results look wrong.
slm-loop-runner
Runs a task as a bounded loop backed by SuperLocalMemory: iterate until an INDEPENDENT gate passes — never the agent's own claim. Delegate here when a task has a checkable acceptance condition (a test suite, a JSON schema, a linter, a reconciliation rule, a security scan) and you want gate-verified completion with an…
agent-design-patterns
LLM 에이전트 설계 패턴 레퍼런스. Anthropic "Building Effective Agents" 5가지 패턴 + 실전 적용 기준. 워크플로우 vs 에이전트 구분, 패턴별 트레이드오프, 프로덕션 배포 체크리스트. 2025 기준.
mcp-advanced-patterns
MCP(Model Context Protocol) 심화 패턴 레퍼런스. 2025 Anthropic 권고 사항 기준. HTTP Streamable Transport, 도구 설계 원칙, 컨텍스트 효율화, 엔터프라이즈 인증, 보안 고려사항. 실제 Claude Code + OpenAkashic MCP 운영 경험 기반.