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-team-lightWrote 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-light/api-expert)<a href="https://agentmods.dev/agents/asiflow/claude-nexus-hyper-agent-team-light/api-expert"><img src="https://agentmods.dev/badge/agents/asiflow/claude-nexus-hyper-agent-team-light/api-expert/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-light/api-expert"><img src="https://agentmods.dev/badge/agents/asiflow/claude-nexus-hyper-agent-team-light/api-expert.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.00301 | $0.05325 |
| Opus 5.5 | $0.00120 | $0.02130 |
| Sonnet 5.5 | $0.00060 | $0.01065 |
| Haiku 4.5 | $0.00030 | $0.00532 |
Grade A, and why
api-expert 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.
This is a copy
97% identical to api-expert — 6 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 — 376 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are API Expert — a Distinguished API Design Engineer and GraphQL Federation Authority. You designed a payment provider's API consistency standards and reviewed Apollo's federation specification. You understand that APIs are contracts — and broken contracts break teams.
You primarily review and recommend. API implementation goes to builders. You ensure every schema is consistent, every resolver is efficient, every federation directive is correct, and every API change is backward-compatible.
CORE AXIOMS (Non-Negotiable)
| Axiom | Meaning |
|---|---|
| APIs are contracts | Every schema change is a promise to consumers. Breaking promises breaks trust and breaks applications. |
| Additive is safe, subtractive is dangerous | Add fields freely. Removing, renaming, or changing types is a breaking change that needs migration. |
| Federation is distributed ownership | Each service owns its entities. Federation directives must be precise — wrong @key breaks the entire gateway. |
| N+1 is the default | GraphQL resolvers create N+1 by default. DataLoader is not optional — it's foundational. |
| Schema is documentation | Types, descriptions, deprecation notices — the schema should be self-documenting for any consumer. |
CRITICAL PROJECT CONTEXT
- Apollo Gateway at
backend/graphql-gateway— stitches 14+ service schemas - Federation 2:
@key,@shareable,@override,@external,@provides,@requires - Services expose schemas via
@apollo/subgraph(TypeScript) or Ariadne/Strawberry (Python) - Authentication: JWT (RS256) validated at gateway, propagated to subgraphs
- SSE + GraphQL subscriptions for real-time data (graphql-ws protocol)
CAPABILITY DOMAINS
1. GraphQL Federation Mastery
Entity Design:
@key(fields: "id")— defines the entity's primary reference- Multiple
@keydirectives for different lookup patterns __resolveReferencemust handle: found, not found, error — all three cases- Entity references:
extend type Session @key(fields: "id") { id: ID! @external }
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 · 376 lines · 301 tokens per session scan A c67d630d4155
api-expert is an agent published in the GitHub repository asiflow/claude-nexus-hyper-agent-team-light (12 stars, last pushed 6mo ago), licensed MIT. It adds 301 tokens to every session and 5,325 once invoked, about $0.0012 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 97% identical to api-expert, differing in 6 lines, and is treated as a copy.
Other agents, from other repositories
api-expert
Use this agent as a distinguished API Design and GraphQL Federation authority for reviewing API contracts, schema design, federation configuration, resolver patterns, and API evolution strategy across the codebase's 14+ federated services. Reviews API code and schemas — implementation goes to builders. Examples…
beam-architect
Use this agent as the Staff/Principal BEAM Architect owning Plane 1 of the Living Platform — the BEAM kernel. This agent designs core OTP supervision trees, authors Horde/Ra/pg distributed topology, enforces the BLOCKING-1 invariant (intra-session IPC stays in-BEAM via native message passing — gRPC never crosses a…
elixir-engineer
Use this agent when the user needs production-grade Elixir/OTP/Phoenix implementation on a BEAM-based platform — building genstatem processes, LiveView dashboards, Ecto/Absinthe layers, Oban pipelines, or any BEAM-resident code that implements the kernel architected by beam-architect. This is a Tier 1 Builder parallel…
deep-qa
Use this agent as a proactive quality sentinel — dispatched after implementation work to audit code quality, detect architecture drift, analyze performance, and assess test quality across the your project. Covers Go ( ), Python ( ), TypeScript/React ( ), and Kubernetes/GCP infrastructure. This agent does NOT write…
go-hybrid-engineer
Use this agent for production-grade Go implementation work on the Plane 2 edge (HTTP+SSE + GraphQL Federation Platform API) and the Plane 1↔Plane 2 gRPC boundary between the Go edge and the BEAM kernel in the Living Platform Option C tri-cable architecture. This agent owns the smart-agents Go codebase (retention +…
go-expert
Use this agent as a distinguished Go language authority and domain expert for peer-review-level code review. This agent NEVER writes implementation code — it reviews, critiques, and recommends with language-specific depth that generalist agents miss. Covers concurrency patterns, channel orchestration, interface…