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 lugassawan/swe-workbench --skill principle-resiliencygit clone --depth 1 https://github.com/lugassawan/swe-workbenchWrote 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/lugassawan/swe-workbench/principle-resiliency)<a href="https://agentmods.dev/skills/lugassawan/swe-workbench/principle-resiliency"><img src="https://agentmods.dev/badge/skills/lugassawan/swe-workbench/principle-resiliency/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/skills/lugassawan/swe-workbench/principle-resiliency"><img src="https://agentmods.dev/badge/skills/lugassawan/swe-workbench/principle-resiliency.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.00126 | $0.02042 |
| Opus 5 | $0.00063 | $0.01021 |
| Sonnet 5 | $0.00025 | $0.00408 |
| Haiku 4.5 | $0.00013 | $0.00204 |
Grade A, and why
principle-resiliency 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.
How it starts
The opening of the file, as written. The whole thing — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resiliency
Distributed systems fail partially, not totally. Resilience is the discipline of staying useful when components, networks, or dependencies degrade.
Failure Domains
A failure domain is the set of components that fail together. Name failure domains before designing for them — unnamed domains produce unnamed blast radii.
- Crash failure — process exits; detectable immediately by the load balancer or orchestrator.
- Slow failure — process responds but takes too long; the most dangerous mode. Threads and connections fill; the caller eventually crashes too.
- Gray/Byzantine failure — process returns wrong data or errors intermittently; hardest to detect.
- Partial failure — some instances or shards fail while others serve normally.
Cascading failure: a degraded dependency holds resources long enough that the caller exhausts its own pools, propagating failure upstream. Root cause is almost always unbounded resource sharing across failure domains.
Bulkheads
Named after ship compartments: isolate resource pools so a breach in one dependency does not exhaust resources for all others.
- Allocate a separate bounded connection pool, semaphore, or thread pool per downstream dependency.
- Never share a single pool across unrelated dependencies — a slow third-party API must not starve database connections.
- In multi-tenant systems, partition queues or workers per tenant to contain noisy-neighbor starvation.
- Size each bulkhead to the dependency's realistic concurrency ceiling, not the caller's maximum.
Fail-Fast vs Fail-Soft
Fail-fast — surface the error immediately without attempting recovery. Use when: an invariant is violated, the operation cannot be retried safely, or the system state is unrecoverable. Examples: config missing at startup, corrupted schema, required auth service unreachable at boot.
Fail-soft — continue serving a degraded response using a fallback, stale cache, or reduced feature set. Use when: the failed component is non-critical and a safe, non-misleading fallback exists. Examples: recommendation service down → return empty list; search unavailable → hide the search bar.
What ships with it
19 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.
- examples/idempotency.cs.md 2.3 KB
- examples/idempotency.go.md 2.4 KB
- examples/idempotency.java.md 2.7 KB
- examples/idempotency.kt.md 2.3 KB
- examples/idempotency.py.md 2.7 KB
- examples/idempotency.rb.md 2.0 KB
- examples/idempotency.rs.md 2.9 KB
- examples/idempotency.swift.md 2.3 KB
- examples/idempotency.ts.md 2.4 KB
- examples/rate-limit.cs.md 2.7 KB
- examples/rate-limit.go.md 2.4 KB
- examples/rate-limit.java.md 3.2 KB
- examples/rate-limit.kt.md 2.3 KB
- examples/rate-limit.py.md 2.9 KB
- examples/rate-limit.rb.md 2.2 KB
- examples/rate-limit.rs.md 2.8 KB
- examples/rate-limit.swift.md 2.6 KB
- examples/rate-limit.ts.md 2.6 KB
- triggers.txt 1011 B
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 · 123 lines · 126 tokens per session scan A 17423abb079f
principle-resiliency is a skill published in the GitHub repository lugassawan/swe-workbench (2 stars, last pushed 4d ago), licensed MIT. It adds 126 tokens to every session and 2,042 once invoked, about $0.0006 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
deploy
Builds and deploys a Power Apps code app to Power Platform. Use when deploying changes, redeploying an existing app, or pushing updates.
release-it
Apply Michael T. Nygard-inspired production reliability rules when designing failure handling, timeouts, retries, circuit breakers, observability, or deployment behavior.
cloudflare-queues
This skill should be used when the user asks to "set up Cloudflare Queues", "create a message queue", "implement queue consumer", "process background jobs", "configure queue retry logic", "publish messages to queue", "implement dead letter queue", or encountering "queue timeout", "message retry", "throughput…
cloudflare-r2
Cloudflare R2 S3-compatible object storage. Use for buckets, uploads, CORS, presigned URLs, or encountering R2ERROR, CORS failures, multipart issues.
manage-file-storage
Swap or remove the file storage provider (S3/MinIO).
code-forge
Generate implementation code from an approved design blueprint or verbal requirements. Composes context anchoring, architecture, clean code, DDD, security, and test quality into an inside-out implementation workflow. Use when moving from design to code, implementing approved contracts, or when the user says…