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 skills/yonatangross/orchestkit/distributed-systemsnpx skills add yonatangross/orchestkit --skill distributed-systemsgit clone --depth 1 https://github.com/yonatangross/orchestkitWrote 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/yonatangross/orchestkit/distributed-systems)<a href="https://agentmods.dev/skills/yonatangross/orchestkit/distributed-systems"><img src="https://agentmods.dev/badge/skills/yonatangross/orchestkit/distributed-systems.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 | $0.00048 | $0.02694 |
| Opus 5 | $0.00024 | $0.01347 |
| Sonnet 5 | $0.00010 | $0.00539 |
| Haiku 4.5 | $0.00005 | $0.00269 |
Grade A, and why
distributed-systems 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 today.
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 — 216 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Distributed Systems Patterns
Comprehensive patterns for building reliable distributed systems. Each category has individual rule files in rules/ loaded on-demand.
Quick Reference
| Category | Rules | Impact | When to Use |
|---|---|---|---|
| Distributed Locks | 1 | CRITICAL | Fencing tokens, owner validation; Redis/Redlock and Postgres advisory via upstream docs |
| Resilience | 3 | CRITICAL | Circuit breakers, retry with backoff, bulkhead isolation |
| Idempotency | 1 | HIGH | Idempotency keys; dedup and database-backed storage via upstream docs |
| Rate Limiting | 2 | HIGH | Token bucket, sliding window; SlowAPI integration via upstream docs |
| Edge Computing | 2 | HIGH | Edge workers, V8 isolates, CDN caching, geo-routing |
| Event-Driven | 2 | HIGH | Event sourcing, CQRS, transactional outbox, sagas |
Total: 11 rules across 6 categories. Removed topics point at first-party sources in Upstream coverage; ork-specific scars live in ${CLAUDE_PLUGIN_ROOT}/skills/distributed-systems/references/ork-delta.md.
Quick Start
# Redis distributed lock with Lua scripts
async with RedisLock(redis_client, "payment:order-123"):
await process_payment(order_id)
# Circuit breaker for external APIs
@circuit_breaker(failure_threshold=5, recovery_timeout=30)
@retry(max_attempts=3, base_delay=1.0)
async def call_external_api():
...
# Idempotent API endpoint
@router.post("/payments")
async def create_payment(
data: PaymentCreate,
idempotency_key: str = Header(..., alias="Idempotency-Key"),
):
return await idempotent_execute(db, idempotency_key, "/payments", process)
# Token bucket rate limiting
limiter = TokenBucketLimiter(redis_client, capacity=100, refill_rate=10)
if await limiter.is_allowed(f"user:{user_id}"):
await handle_request()
Distributed Locks
What ships with it
24 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.
- metadata.json 568 B
- references/ork-delta.md 2.3 KB
- rules/_sections.md 2.2 KB
- rules/_template.md 339 B
- rules/edge-caching.md 3.0 KB
- rules/edge-workers.md 2.6 KB
- rules/event-messaging.md 3.7 KB
- rules/event-sourcing.md 3.8 KB
- rules/idempotency-keys.md 4.5 KB
- rules/locks-fencing-tokens.md 4.3 KB
- rules/ratelimit-sliding-window.md 3.6 KB
- rules/ratelimit-token-bucket.md 3.9 KB
- rules/resilience-bulkhead.md 4.1 KB
- rules/resilience-circuit-breaker.md 4.7 KB
- rules/resilience-retry-backoff.md 4.1 KB
- scripts/bulkhead.py 14 KB runs code
- scripts/circuit-breaker.py 12 KB runs code
- scripts/distributed-lock-template.py 11 KB runs code
- scripts/idempotency-middleware-template.py 11 KB runs code
- scripts/llm-fallback-chain.py 14 KB runs code
- scripts/redis-rate-limiter.py 10 KB runs code
- scripts/retry-handler.py 14 KB runs code
- scripts/token-budget.py 15 KB runs code
- test-cases.json 6.0 KB
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.
- today First seen · 216 lines · 48 tokens per session scan A 9ee2b337e480
distributed-systems is a skill published in the GitHub repository yonatangross/orchestkit (225 stars, last pushed today), licensed MIT. It adds 48 tokens to every session and 2,694 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
error-handling
Use when designing the reaction to a class of failures — typed error taxonomies, retry/backoff/timeout policy, circuit breakers, React/Next error boundaries, and the user-message vs operator-log split. NOT diagnosing one specific crash (that is debug), NOT logs/metrics/traces (that is observability), NOT the wire…
error-handling
Error handling patterns. Exception hierarchies, Result types, structured error responses, retry strategies, circuit breakers.
backend-resilience-patterns
Use this skill when the user says 'resilience', 'circuit breaker', 'retry', 'bulkhead', 'timeout', 'fallback', 'resilience4j', 'fault tolerance', 'rate limiter', 'backoff', 'retry strategy', 'bulkhead pattern'. This skill applies production fault-tolerance patterns: circuit breaker, retry with backoff, bulkhead…
api-rate-limit-handler
Implement bounded, idempotency-aware API throttling, backoff, and retry handling for 429 and transient 5xx responses.
API Gateway Testing
API gateway testing skill covering rate limiting validation, request routing, authentication proxy testing, load balancing verification, circuit breaker testing, and gateway configuration validation for Kong, Envoy, and AWS API Gateway.
moonbit-agent-guide
Guide for writing, refactoring, and testing MoonBit projects. Use when working in MoonBit modules or packages, organizing MoonBit files, using moon tooling (build/check/run/test/doc/ide etc.), or following MoonBit-specific layout, documentation, and testing conventions.