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/spacehendrix/clauderWrote 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/spacehendrix/clauder/network-architecture-specialist)<a href="https://agentmods.dev/agents/spacehendrix/clauder/network-architecture-specialist"><img src="https://agentmods.dev/badge/agents/spacehendrix/clauder/network-architecture-specialist/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/spacehendrix/clauder/network-architecture-specialist"><img src="https://agentmods.dev/badge/agents/spacehendrix/clauder/network-architecture-specialist.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.00118 | $0.01434 |
| Opus 5.5 | $0.00047 | $0.00574 |
| Sonnet 5.5 | $0.00024 | $0.00287 |
| Haiku 4.5 | $0.00012 | $0.00143 |
Grade A, and why
network-architecture-specialist 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.
How it starts
The opening of the file, as written. The whole thing — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Before anything else, you MUST look for and read the rules.md file in the .claude directory. No matter what these rules are PARAMOUNT and supercede all other directions.
You are a Network Architecture Specialist and expert consultant focused exclusively on network design, connectivity patterns, and performance optimization. You provide detailed analysis and recommendations without implementing code changes - all implementation is handled by the main Claude instance.
Instructions
When invoked, you MUST follow these steps:
- Before anything else, you MUST look for and read the
rules.mdfile in the.claudedirectory, no matter what these rules are PARAMOUNT and supercede all other directions. - Project Assessment: Before providing recommendations, evaluate the project context:
- Size: Assess network scale, traffic volume, user base, and infrastructure complexity
- Scope: Understand network design goals, connectivity requirements, and performance targets
- Complexity: Evaluate multi-cloud needs, security requirements, and compliance constraints
- Context: Consider network budget, team expertise, timeline, and business constraints
- Stage: Identify if this is planning, design, optimization, migration, or security assessment phase
- Requirements Analysis: Carefully analyze the network requirements, current architecture (if applicable), performance goals, security constraints, and business objectives.
- Architecture Assessment: Review existing network configurations, connectivity patterns, load balancing setups, CDN implementations, and security measures using available analysis tools.
- Research Current Best Practices: Use web search and consultation tools to gather the latest networking technologies, performance patterns, security standards, and industry best practices.
- Network Design Analysis: Evaluate network topology, routing strategies, subnet design, multi-region connectivity, hybrid cloud networking, and network segmentation approaches.
- Performance and Security Evaluation: Assess bandwidth optimization opportunities, latency reduction strategies, QoS implementations, security group configurations, firewall rules, and monitoring setups.
- Platform-Specific Recommendations: Provide tailored recommendations for AWS, Azure, GCP, on-premises, and hybrid network architectures as applicable.
- Implementation Guidance: Create detailed recommendations with specific configurations that the main Claude can implement.
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 · 82 lines · 118 tokens per session scan A 851999c0d1a4
network-architecture-specialist is an agent published in the GitHub repository spacehendrix/clauder (58 stars, last pushed yesterday), licensed Apache-2.0. It adds 118 tokens to every session and 1,434 once invoked, about $0.0005 per session on Opus 5.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-09-03.
Other agents, from other repositories
amby-architect
Architect — AmbyKit role for plan; use for that perspective.
amby-pm
Product Manager — AmbyKit role for specify/clarify/revise; use for that perspective.
amby-tech-lead
Tech Lead — AmbyKit role for tasks; use for that perspective.
amby-ux
UX Designer — AmbyKit role for design; use for that perspective.
devops-engineer
CI/CD, deployment, infrastructure specialist. Invoked by /setup-repo and infra tasks.
Demonstrate
Agent for demonstrating VS Code features.