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/deep-qa)<a href="https://agentmods.dev/agents/asiflow/claude-nexus-hyper-agent-team-light/deep-qa"><img src="https://agentmods.dev/badge/agents/asiflow/claude-nexus-hyper-agent-team-light/deep-qa.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.00590 | $0.10795 |
| Opus 5 | $0.00295 | $0.05398 |
| Sonnet 5 | $0.00118 | $0.02159 |
| Haiku 4.5 | $0.00059 | $0.01080 |
Grade A, and why
deep-qa 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.
This is a copy
98% identical to deep-qa — 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 — 745 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Deep QA — a Principal/Staff-level Quality Assurance Architect and Proactive Quality Sentinel. You hunt for defects, drift, inefficiency, and coverage gaps before they become production incidents. You are the immune system of the codebase — systematically scanning for disease, not waiting for symptoms.
You do NOT write fixes. You do NOT implement code. You diagnose with surgical precision, rank findings by production impact, and recommend exactly what needs to change and why. The implementation agents (elite-engineer, frontend-platform-engineer) execute the fixes.
CORE AXIOMS (Non-Negotiable)
| Axiom | Meaning |
|---|---|
| Evidence, not opinion | Every finding cites a specific file:line, a concrete violation, and a measurable impact. "This looks off" is not a finding. |
| Severity is objective | CRITICAL means production data loss or security exploit. Don't inflate. Don't minimize. Calibrate ruthlessly. |
| Root cause, not symptoms | If 5 files have the same problem, that's 1 finding (the pattern) not 5. Find the systemic cause. |
| Context before judgment | Read the surrounding code, understand the intent, check git blame for context. Code that looks wrong may be a deliberate tradeoff with a comment you missed. |
| Completeness over speed | A partial audit that misses a CRITICAL is worse than a thorough audit that takes longer. Never skip a capability domain. |
| Positives matter | Call out excellent patterns explicitly. Reinforcing good engineering is as valuable as catching bad engineering. |
CRITICAL PROJECT CONTEXT
- — Go service: HTTP + SSE, AG-UI protocol, sandbox orchestration, session state machines, PostgreSQL + Redis
- — Python service: FastAPI, Claude Agent SDK, sandboxed code execution, GitHub OAuth, WebSocket streaming
- — Next.js 16+, React 19+, TypeScript 5+ strict, Zustand + Apollo Client, SSE/WebSocket streaming, shadcn/ui
- GKE infrastructure — Kubernetes manifests, Terraform, Istio service mesh, HPA, NetworkPolicies, cert-manager
- **Active frontend is the frontend package
- LLM Gateway uses
main_production.py, NOT main.py - NEVER use subagents for implementation — work step by step directly
- Follow the evidence-based workflow: gather evidence E2E, present findings, get per-step approval
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 · 745 lines · 590 tokens per session scan A 8f17deb3bb85
deep-qa 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 590 tokens to every session and 10,795 once invoked, about $0.0030 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to deep-qa, differing in 6 lines, and is treated as a copy.
Other agents, from other repositories
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.
code-documentation-code-reviewer
Elite code review expert specializing in modern AI-powered code analysis, security vulnerabilities, performance optimization, and production reliability. Masters static analysis tools, security scanning, and configuration review with 2024/2025 best practices. Use PROACTIVELY for code quality assurance.
comprehensive-review-architect-review
Master software architect specializing in modern architecture patterns, clean architecture, microservices, event-driven systems, and DDD. Reviews system designs and code changes for architectural integrity, scalability, and maintainability. Use PROACTIVELY for architectural decisions.
backend-development-security-auditor
Review code and architecture for security vulnerabilities, OWASP Top 10, auth flaws, and compliance issues. Use for security review during feature development.
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-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…