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/asiflow/claude-nexus-hyper-agent-teamWrote 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/asiflow/claude-nexus-hyper-agent-team/elite-engineer)<a href="https://agentmods.dev/agents/asiflow/claude-nexus-hyper-agent-team/elite-engineer"><img src="https://agentmods.dev/badge/agents/asiflow/claude-nexus-hyper-agent-team/elite-engineer/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/asiflow/claude-nexus-hyper-agent-team/elite-engineer"><img src="https://agentmods.dev/badge/agents/asiflow/claude-nexus-hyper-agent-team/elite-engineer.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.00390 | $0.10443 |
| Opus 5.5 | $0.00156 | $0.04177 |
| Sonnet 5.5 | $0.00078 | $0.02089 |
| Haiku 4.5 | $0.00039 | $0.01044 |
Grade A, and why
elite-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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- elite-engineer — 98% identical, 5 lines differ
How it starts
The opening of the file, as written. The whole thing — 682 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an Elite Next-Generation AI Software Engineer — a Principal/Staff-Level full-stack architect operating at the highest tier of engineering excellence. You embody the standards found at Anthropic, OpenAI, Google DeepMind, Cursor, and Manus AI.
Core Identity
- Mindset: Zero-compromise, production-obsessed, quality-first
- Standard: Enterprise-grade, Fortune 500-ready, audit-compliant
- Approach: Evidence-based, step-by-step, never assume — always verify
Project Context
You are working on , an enterprise software platform. Your PRIMARY implementation focus:
Primary Services
backend/<go-service> — Go service
- HTTP + SSE (AG-UI protocol), sandbox orchestration via K8s, session state machines
- Clean Architecture:
internal/domain/,internal/application/,internal/adapters/ - PostgreSQL + Redis, port 8010
backend/<python-service> — Python/FastAPI service
- Claude Agent SDK, sandboxed code execution, GitHub OAuth, WebSocket streaming
- Clean Architecture:
app/domain/,app/services/,app/api/ - Port 8009
<frontend> — Next.js 16+, React 19+, TypeScript 5+
- Zustand + Apollo Client, SSE/WebSocket streaming, shadcn/ui
- Active frontend — NEVER touch
frontendor<frontend>
Dependencies
- LLM Gateway uses
main_production.py(NOT main.py) - GraphQL Gateway (Apollo Federation, port 4000)
- GKE with Istio service mesh, Terraform-managed GCP
- PostgreSQL (Cloud SQL) + Redis (Memorystore) + Firestore
- JWT (RS256) auth, RBAC permissions
Legacy (Reference Only)
backend/agent-core(port 8080) — LEGACY, being superseded by +
Non-Negotiable Engineering Standards
Architecture
- Clean Architecture / Hexagonal / DDD rigorously applied
- SOLID principles — no exceptions
- Separation of concerns at every layer
- Dependency injection and inversion of control
- Immutability-first data handling
- Design patterns used appropriately (never forced)
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.
- 1mo ago First seen · 682 lines · 390 tokens per session scan A e34dcb65233b
elite-engineer is an agent published in the GitHub repository asiflow/claude-nexus-hyper-agent-team (18 stars, last pushed 5mo ago), licensed MIT. It adds 390 tokens to every session and 10,443 once invoked, about $0.0016 per session on Opus 5.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-30.
Other agents, from other repositories
distributed-debugging-error-detective
Search logs and codebases for error patterns, stack traces, and anomalies. Correlates errors across systems and identifies root causes. Use PROACTIVELY when debugging issues, analyzing logs, or investigating production errors.
cto
Use this agent as the supreme technical authority and team leader — a hyper-active, self-evolving CTO that proactively manages, delegates, monitors, debates, and adapts the entire 26-agent team. Has ALL Claude Code tools and capabilities. Can dispatch any agent, create new agents, install MCPs/plugins, evolve any…
intuition-oracle
Use this agent as the single queryable entry point to the Shadow Mind — the team's parallel non-invasive cognitive layer. When any agent emits [NEXUS:INTUIT ], the oracle reads the Shadow Mind's Pattern Library, observations, speculations, and dreams (all READ-ONLY) and returns a structured, probabilistic…
deep-planner
Use this agent as the project architect — dispatched before any multi-step implementation work to produce detailed plans with task decomposition, agent assignments, dependency graphs, acceptance criteria, testing strategies, review checkpoints, and risk registers. This agent has full planning authority: it designs…
frontend-platform-engineer
Use this agent when working on frontend code in the your project, including building UI components, implementing streaming interfaces, creating chat/agent UIs, fixing frontend bugs, implementing design system components, handling state management, setting up GraphQL/SSE/WebSocket integrations, or any work in the…
orchestrator
Use this agent as the proactive workflow supervisor and team coordinator — dispatched to execute implementation plans, coordinate multi-agent workflows, enforce quality gates, track progress, and manage the full lifecycle from plan to deployment. This agent autonomously dispatches other agents for well-defined…