A command-line tool for checking and changing Dapr resiliency settings—the rules that help services cope with failures. It covers retries, time limits, and circuit breakers, which temporarily stop calls to a failing service.

Use it to inspect resiliency YAML files, apply policy changes, and test retry, timeout, and circuit-breaker behavior in a Dapr application.

It helps find settings that retry too aggressively, stop too soon, or are missing. This reduces the chance that one failing dependency causes more failures or overload.

resiliency — Command for Claude Code by Sahib-Sawhney-WH

Install

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.

Clone the repo

git clone --depth 1 https://github.com/Sahib-Sawhney-WH/sahibs-claude-plugin-marketplace

Made for: Claude Code.

Or install dapr, the plugin that ships this one along with the rest of its 9 skills, 14 commands, 8 agents.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/sahib-sawhney-wh/sahibs-claude-plugin-marketplace/resiliency/github.svg)](https://agentmods.dev/commands/sahib-sawhney-wh/sahibs-claude-plugin-marketplace/resiliency)

Your own site

<a href="https://agentmods.dev/commands/sahib-sawhney-wh/sahibs-claude-plugin-marketplace/resiliency"><img src="https://agentmods.dev/badge/commands/sahib-sawhney-wh/sahibs-claude-plugin-marketplace/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/sahib-sawhney-wh/sahibs-claude-plugin-marketplace/resiliency"><img src="https://agentmods.dev/badge/commands/sahib-sawhney-wh/sahibs-claude-plugin-marketplace/resiliency.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 21 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,804 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00021	$0.01804
Opus 5.5	$0.00008	$0.00722
Sonnet 5.5	$0.00004	$0.00361
Haiku 4.5	$0.00002	$0.00180

Measured 2mo ago against content hash d3b1be9be63f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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 2mo 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.

plugins/dapr/commands/resiliency.md · 297 lines

How it starts

The opening of the file, as written. The whole thing — 297 lines — stays where its author put it; the contents beside it link to each section on GitHub.

DAPR Resiliency Manager

Manage resiliency configurations for your DAPR applications to ensure fault tolerance and graceful degradation.

Behavior

When the user runs /dapr:resiliency:

1. Analyze Mode (Default)

Analyze the current resiliency configuration:

DAPR Resiliency Analysis
=========================

Configuration Files Found:
  ✓ resiliency.yaml (dapr.io/v1alpha1)
  ✓ components/statestore.yaml
  ✓ components/pubsub.yaml

Policy Analysis:
-----------------

Retry Policies (3 defined):
  ✓ serviceRetry
    - Type: exponential
    - Max Retries: 5
    - Max Interval: 30s
    Status: GOOD

  ⚠ stateStoreRetry
    - Type: constant
    - Duration: 500ms
    - Max Retries: 10
    Status: WARNING - Consider exponential backoff for production

  ✗ externalApiRetry
    - Type: constant
    - Duration: 100ms
    - Max Retries: 20
    Status: PROBLEM - Too aggressive, may cause rate limiting

Timeout Policies (2 defined):
  ✓ serviceTimeout: 30s (reasonable)
  ⚠ externalTimeout: 5s (may be too short for external APIs)

Circuit Breaker Policies (1 defined):
  ✓ serviceBreaker
    - Threshold: 5 consecutive failures
    - Recovery: 60s
    Status: GOOD

Missing Policies:
  ⚠ No circuit breaker for state store operations
  ⚠ No timeout policy for pub/sub

Target Coverage:
-----------------
  Apps: 2/3 covered (order-service, payment-service)
  Components: 1/2 covered (statestore)

  Uncovered:
    - notification-service (no resiliency)
    - pubsub (no policies)

Recommendations:
-----------------
1. Add circuit breaker for statestore to prevent cascade failures
2. Increase externalTimeout to 30s for third-party APIs
3. Change externalApiRetry to exponential backoff
4. Add resiliency policies for notification-service

2. Apply Mode

Apply a resiliency pattern to the project:

/dapr:resiliency apply --pattern microservices

Applying 'microservices' resiliency pattern...

Created: resiliency.yaml

Applied policies:
  ✓ serviceRetry (exponential, 5 retries, 30s max)
  ✓ serviceTimeout (30s)
  ✓ serviceCircuitBreaker (5 failures, 60s recovery)

Configured targets:
  ✓ All apps: serviceTimeout + serviceRetry + serviceCircuitBreaker
  ✓ statestore: stateStoreRetry + stateStoreCircuitBreaker
  ✓ pubsub: pubsubRetry

Next steps:
  1. Review resiliency.yaml and customize values
  2. Run 'dapr run' to test locally
  3. Use '/dapr:resiliency test' to validate behavior

Read the full file on GitHub · 297 lines

Changes

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.

2mo ago First seen · 297 lines · 21 tokens per session scan A d3b1be9be63f

Subscribe to this mod's changes

resiliency is a command published in the GitHub repository Sahib-Sawhney-WH/sahibs-claude-plugin-marketplace (4 stars, last pushed 10mo ago), licensed MIT. It adds 21 tokens to every session and 1,804 once invoked, about $0.0001 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-08-31.

Backend and APIs DevOps and cloud

resiliency next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
resiliencySahib-Sawhney-WH/sahibs-claude-plugin-marketplace	Command	4	10mo ago	MIT	A	21	Claude Code
initfcakyon/claude-codex-settings	Command	1.2k	yesterday	Apache-2.0	A	0	Claude Code
http-serviceMadAppGang/magus	Command	14	yesterday	MIT	A	27	Claude Code
buildAzure/ai-gateway	Command	5	10d ago	MIT	A	0	Claude Code
api-contract-reviewMozurok/fhorja.dev	Command	10	28d ago	MIT	A	64	Claude Code
start-10-1minicoohei/ai-agent-camp	Command	347	1mo ago	none	A	2	Claude Code
fastapimfmezger/ai_agent_dotfiles	Command	7	3mo ago	MIT	A	84	Claude Code, Gemini CLI