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/Sahib-Sawhney-WH/sahibs-claude-plugin-marketplaceWrote 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/commands/sahib-sawhney-wh/sahibs-claude-plugin-marketplace/resiliency)<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.
<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>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 | $0.00010 | $0.00902 |
| Sonnet 5 | $0.00004 | $0.00361 |
| Haiku 4.5 | $0.00002 | $0.00180 |
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 12d 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 — 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
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.
- 12d ago First seen · 297 lines · 21 tokens per session scan A d3b1be9be63f
resiliency is a command published in the GitHub repository Sahib-Sawhney-WH/sahibs-claude-plugin-marketplace (4 stars, last pushed 8mo ago), licensed MIT. It adds 21 tokens to every session and 1,804 once invoked, about $0.0001 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-31.
Other commands, from other repositories
init
Initialize configurations for Supabase local development.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
start-10-1
A guided lesson on setting up clasp, a command-line tool for managing Google Apps Script projects, and connecting it to Google’s Apps Script API.
api-contract-review
Review an API contract (endpoints, request/response shapes, error codes, auth model) BEFORE implementation for naming consistency, versioning, pagination, idempotency, and alignment with existing endpoints. Distinct from review-hard (post-implementation risk) and repo-consistency-sweep (pattern matching on written…
fastapi
FastAPI application design and implementation conventions. Use this skill when building, updating, or reviewing FastAPI services, routers, dependencies, request/response schemas, streaming endpoints, or API tests. Trigger on FastAPI-specific work such as path operation design, dependency injection, response models…
build
Discover an AI Gateway's models and MCP tools, retrieve a credential, and integrate them into your app — call a model, connect MCP tools, or scaffold a runnable agent.