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/vimalk0703/shipworthy/resilience-patternsnpx skills add Vimalk0703/shipworthy --skill resilience-patternsgit clone --depth 1 https://github.com/Vimalk0703/shipworthyWrote 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/vimalk0703/shipworthy/resilience-patterns)<a href="https://agentmods.dev/skills/vimalk0703/shipworthy/resilience-patterns"><img src="https://agentmods.dev/badge/skills/vimalk0703/shipworthy/resilience-patterns.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.00041 | $0.02286 |
| Opus 5 | $0.00020 | $0.01143 |
| Sonnet 5 | $0.00008 | $0.00457 |
| Haiku 4.5 | $0.00004 | $0.00229 |
Grade A, and why
resilience-patterns scanned grade A with 1 finding 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 5d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
response = requests.get("https://api.partner.com/data", timeout=5) How it starts
The opening of the file, as written. The whole thing — 294 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resilience Patterns
Core Principle
Every external call will eventually fail. Resilience is not about preventing failure -- it is about controlling the blast radius and recovering quickly.
1. Circuit Breaker
What it does: Stops calling a failing downstream service, giving it time to recover instead of overwhelming it with doomed requests.
States: CLOSED (normal) -> OPEN (failing, reject calls) -> HALF-OPEN (test with limited traffic).
When to apply: Any synchronous call to an external service, database, or third-party API.
TypeScript Example (using cockatiel)
import { CircuitBreakerPolicy, SamplingBreaker, handleAll } from 'cockatiel';
const breaker = new CircuitBreakerPolicy(handleAll, {
halfOpenAfter: 10_000, // Try again after 10s
breaker: new SamplingBreaker({
threshold: 0.5, // Open when 50% of requests fail
duration: 30_000, // Over a 30s window
minimumRps: 5, // Need at least 5 req/s to evaluate
}),
});
breaker.onBreak(() => console.warn('Circuit OPEN -- downstream is failing'));
breaker.onHalfOpen(() => console.info('Circuit HALF-OPEN -- testing downstream'));
breaker.onReset(() => console.info('Circuit CLOSED -- downstream recovered'));
const result = await breaker.execute(() => callDownstreamService());
Python Example
import circuitbreaker
@circuitbreaker.circuit(failure_threshold=5, recovery_timeout=30)
def call_downstream_service():
response = requests.get("https://api.partner.com/data", timeout=5)
response.raise_for_status()
return response.json()
# Usage with fallback
try:
data = call_downstream_service()
except circuitbreaker.CircuitBreakerError:
data = get_cached_or_default_data()
2. Bulkhead
What it does: Isolates failures by partitioning resources (thread pools, connection pools, rate limits) so one failing dependency cannot exhaust resources needed by others.
When to apply: A service calls multiple downstream dependencies and you need to prevent one slow dependency from starving others.
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.
- 5d ago First seen · 294 lines · 41 tokens per session scan A 54221a768eb5
resilience-patterns is a skill published in the GitHub repository Vimalk0703/shipworthy (7 stars, last pushed 4mo ago), licensed MIT. It adds 41 tokens to every session and 2,286 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
hedgehog-core-design
Use on full-stack-app and landing-page alike only when neither shipped core fits a project that is still building something real — picks the stack and designs the layer sequence for it, and writes .hedgehog/core.yaml. Invoked by the planner agent as Phase 0's third outcome, after the vendored BMAD shelf has run; don't…
hedgehog-planning-intake
Use on any core for first-run planning intake — Phase 0 runs the vendored BMAD-METHOD planning shelf, shared by every core, and Phase 1 (mining 04-prd.md into intent records plus the Add-ons/sync-and-remote-entities decision) is full-stack-app's and pwa-app's shared procedure — identical mechanics, a different…
inbound-triage
Maintainer-only. Use when triaging inbound GitHub issues and pull requests on skyf0xx/hedgehog — "triage the issues", "check the PRs", "review inbound", "what's in the queue". Reads each item read-only, judges it for security and for whether it is real, then fixes and closes or comments and closes. Not part of the…
bmad-product-brief
Create, update, or validate a product brief. Use when the user wants help producing, editing, or validating a brief.
bmad-revendor
Maintainer-only. Use when re-vendoring vendor-skills/BMAD/ against a newer BMAD-METHOD commit — "update BMAD", "re-vendor BMAD", "bump the BMAD pin". Not part of the Hedgehog discipline a consuming project copies; this only applies to the Hedgehog repo itself.
bmad-deep-recon
Decision-grade research, three ways: draft a deep-research prompt for the user to run in their own tool (ChatGPT, Gemini, Grok, Perplexity, …), process a finished research report — file it, distill a succinct cited summary with metadata that downstream skills consume without reprocessing — or run the research here…