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.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.00301 | $0.05325 |
| Opus 5 | $0.00151 | $0.02662 |
| Sonnet 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 7d 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.
- 7d 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 4mo ago), licensed MIT. It adds 301 tokens to every session and 5,325 once invoked, about $0.0015 per session on Opus 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…
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…
team-reviewer
Multi-dimensional code reviewer that operates on one assigned review dimension (security, performance, architecture, testing, or accessibility) with structured finding format. Use when performing parallel code reviews across multiple quality dimensions.
api-scaffolding-backend-architect
Expert backend architect specializing in scalable API design, microservices architecture, and distributed systems. Masters REST/GraphQL/gRPC APIs, event-driven architectures, service mesh patterns, and modern backend frameworks. Handles service boundary definition, inter-service communication, resilience patterns, and…
backend-api-security-backend-security-coder
Expert in secure backend coding practices specializing in input validation, authentication, and API security. Use PROACTIVELY for backend security implementations or security code reviews.
temporal-python-pro
Master Temporal workflow orchestration with Python SDK. Implements durable workflows, saga patterns, and distributed transactions. Covers async/await, testing strategies, and production deployment. Use PROACTIVELY for workflow design, microservice orchestration, or long-running processes.