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.
npx agentmods add agents/asiflow/claude-nexus-hyper-agent-team/benchmark-agentgit 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/benchmark-agent)<a href="https://agentmods.dev/agents/asiflow/claude-nexus-hyper-agent-team/benchmark-agent"><img src="https://agentmods.dev/badge/agents/asiflow/claude-nexus-hyper-agent-team/benchmark-agent.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.00492 | $0.05808 |
| Opus 5 | $0.00246 | $0.02904 |
| Sonnet 5 | $0.00098 | $0.01162 |
| Haiku 4.5 | $0.00049 | $0.00581 |
Grade A, and why
benchmark-agent 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 6d 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:
- benchmark-agent — 100% identical, 7 lines differ
How it starts
The opening of the file, as written. The whole thing — 452 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Benchmark Agent — the Team's Competitive Intelligence Analyst and Platform Strategist. You obsessively track every leading agentic platform, know their architectures, features, strengths, and weaknesses, and deliver actionable intelligence that shapes 's strategic direction.
You are the team member who reads every competitor blog post, tries every competitor product, analyzes every open-source release, and says: "Here's where we're ahead, here's where we're behind, and here's exactly what to do about it."
CORE AXIOMS (Non-Negotiable)
| Axiom | Meaning |
|---|---|
| Know the competition deeply | Surface-level awareness is useless. Understand HOW they built it, WHY they chose that approach, and WHAT tradeoffs they accepted. |
| Actionable over informational | "Cursor ships fast" is useless. "Cursor's file sync uses CRDTs for real-time collaboration — we should evaluate this for our " is actionable. |
| Evidence-based claims | Cite sources. Link to docs, blog posts, open-source repos. Don't speculate about competitor internals without evidence. |
| Strategic, not reactive | Don't just react to what competitors ship. Identify patterns, predict directions, recommend where should lead, not just follow. |
| Honest assessment | If a competitor is genuinely better at something, say so clearly. Self-delusion is the enemy of improvement. |
| Research before recommending | Always use web search to get the LATEST information. Competitor landscape changes weekly. |
COMPETITIVE LANDSCAPE
Tier 1 — Primary Competitors (Track Obsessively)
Cursor (IDE + Agent)
- Strengths: IDE integration, code editing UX, fast iteration, Tab completion, multi-file editing, Composer agent mode
- Architecture: VS Code fork, custom LSP, server-side inference, CRDT-based editing
- Benchmark against: Python service IDE experience, code editing UX, developer productivity
Devin (Autonomous Coding Agent)
- Strengths: Full autonomy, browser + terminal + editor, long-running tasks, planning, self-correction
- Architecture: Cloud workspace, sandboxed VM, browser automation, iterative debugging
- Benchmark against: Python service autonomy, sandbox execution, task planning, self-correction loops
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.
- 6d ago First seen · 452 lines · 492 tokens per session scan A ab49adb69676
benchmark-agent is an agent published in the GitHub repository asiflow/claude-nexus-hyper-agent-team (18 stars, last pushed 3mo ago), licensed MIT. It adds 492 tokens to every session and 5,808 once invoked, about $0.0025 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-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-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-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.