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 skills add proyecto26/system-design-skills --skill load-balancinggit clone --depth 1 https://github.com/proyecto26/system-design-skillsWrote 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/skills/proyecto26/system-design-skills/load-balancing)<a href="https://agentmods.dev/skills/proyecto26/system-design-skills/load-balancing"><img src="https://agentmods.dev/badge/skills/proyecto26/system-design-skills/load-balancing.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.00146 | $0.03140 |
| Opus 5 | $0.00073 | $0.01570 |
| Sonnet 5 | $0.00029 | $0.00628 |
| Haiku 4.5 | $0.00015 | $0.00314 |
Grade A, and why
load-balancing 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.
How it starts
The opening of the file, as written. The whole thing — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Load Balancing
Spread incoming requests across a pool of identical backends so no single server is the bottleneck or the single point of failure. Get it wrong and the balancer becomes the SPOF it was meant to remove, routes traffic to dead servers, or amplifies an outage by hammering a backend that is already on its knees.
When to reach for this
Reach for a balancer when more than one backend serves the same role and traffic must be split across them; when a single entry point is a SPOF to eliminate; to add or remove servers without clients noticing (the enabler for the stateless tier and autoscaling); or to put one public address in front of a private fleet, with TLS termination, health-gating, and routing in one place.
When NOT to
One backend that comfortably handles peak load needs no balancer yet — adding one
is a new component, a new failure mode, and a new thing to operate (YAGNI). If the
real bottleneck is the database or a single hot shard, a balancer in front of the
web tier solves nothing; diagnose the actual constraint first (→ back-of-the-envelope).
Cross-region traffic steering is usually DNS/anycast at the edge, not an L4/L7
balancer (→ content-delivery). Per-client request limiting is a policy concern
owned by resilience-failure, not the balancing algorithm.
Clarify first
- Protocol & layer need — raw TCP/UDP throughput (L4) or HTTP-aware routing by path/host/header/cookie (L7)? This picks the balancer type.
- State — is the backend stateless, or does a session live on one server (forcing affinity)? Moving state out is almost always the better answer.
- Peak QPS & connection count — one fat connection stream or many short
requests? Drives algorithm and balancer sizing (→
back-of-the-envelope). - Health signal — what does "healthy" mean (TCP accept? a
/healthz200? a deep dependency check?) and how fast must a dead node leave the pool? - TLS — terminate at the balancer (offload backends, inspect L7) or pass through end-to-end (compliance/mTLS)?
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 212 lines · 146 tokens per session scan A 6dd2891817b0
load-balancing is a skill published in the GitHub repository proyecto26/system-design-skills (69 stars, last pushed 3mo ago), licensed MIT. It adds 146 tokens to every session and 3,140 once invoked, about $0.0007 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 skills, from other repositories
data-engineering
Builds and operates data pipelines — ingestion, transformation, orchestration, quality testing, and reliability of data delivery. Use this to design or debug a pipeline, decide batch versus streaming, add data quality checks, handle late or duplicate data, or work out why a dashboard's numbers changed without anyone…
api-design
Designs interfaces that survive their consumers — resource modeling, errors, versioning, pagination, and compatibility. Use this to design a new API, review one before it ships, decide how to version or deprecate, fix an interface consumers keep misusing, or work out whether a change is breaking.
build-falco-web-app
Build or modify a Falco web application in idiomatic F#, using functional routing, request and response helpers, explicit ASP.NET Core integration, security boundaries, and focused tests.
build-giraffe-web-app
Build or modify a Giraffe web application in idiomatic F#, using composable HttpHandler functions, explicit ASP.NET Core integration, configuration, authentication, and focused endpoint tests.
build-oxpecker-web-app
Build or modify an Oxpecker web application in idiomatic F#, using endpoint routing, functional EndpointHandler and EndpointMiddleware composition, ASP.NET Core metadata, and focused endpoint tests.
swift-openapi-client-workflow
Build, integrate, test, and diagnose Swift OpenAPI Generator clients in Apple-platform apps and Swift packages using OpenAPIURLSession, OpenAPIRuntime, URLSessionTransport, SwiftPM plugins, Apple docs, Dash docsets, and clear handoffs to server-side Swift OpenAPI workflows when the API contract or server transport…