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.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.00390 | $0.10443 |
| Opus 5 | $0.00195 | $0.05221 |
| Sonnet 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 8d 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.
- 8d 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 3mo ago), licensed MIT. It adds 390 tokens to every session and 10,443 once invoked, about $0.0019 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-30.
Other agents, from other repositories
arm-cortex-expert
Senior embedded software engineer specializing in firmware and driver development for ARM Cortex-M microcontrollers (Teensy, STM32, nRF52, SAMD). Decades of experience writing reliable, optimized, and maintainable embedded code with deep expertise in memory barriers, DMA/cache coherency, interrupt-driven I/O, and…
c4-code
Expert C4 Code-level documentation specialist. Analyzes code directories to create comprehensive C4 code-level documentation including function signatures, arguments, dependencies, and code structure. Use when documenting code at the lowest C4 level for individual directories and code modules.
c4-container
Expert C4 Container-level documentation specialist. Synthesizes Component-level documentation into Container-level architecture, mapping components to deployment units, documenting container interfaces as APIs, and creating container diagrams. Use when synthesizing components into deployment containers and documenting…
c4-component
Expert C4 Component-level documentation specialist. Synthesizes C4 Code-level documentation into Component-level architecture, defining component boundaries, interfaces, and relationships. Creates component diagrams and documentation. Use when synthesizing code-level documentation into logical components.
c4-context
Expert C4 Context-level documentation specialist. Creates high-level system context diagrams, documents personas, user journeys, system features, and external dependencies. Synthesizes container and component documentation with system documentation to create comprehensive context-level architecture. Use when creating…
conductor-validator
Validates Conductor project artifacts for completeness, consistency, and correctness. Use after setup, when diagnosing issues, or before implementation to verify project context.