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 Bilal140202/the-lord-of-the-skills --skill aws-samples__sample-well-architected-skills-and-steeringgit clone --depth 1 https://github.com/Bilal140202/the-lord-of-the-skillsWrote 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/bilal140202/the-lord-of-the-skills/aws-samples__sample-well-architected-skills-and-steering)<a href="https://agentmods.dev/skills/bilal140202/the-lord-of-the-skills/aws-samples__sample-well-architected-skills-and-steering"><img src="https://agentmods.dev/badge/skills/bilal140202/the-lord-of-the-skills/aws-samples__sample-well-architected-skills-and-steering/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/bilal140202/the-lord-of-the-skills/aws-samples__sample-well-architected-skills-and-steering"><img src="https://agentmods.dev/badge/skills/bilal140202/the-lord-of-the-skills/aws-samples__sample-well-architected-skills-and-steering.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.00039 | $0.02790 |
| Opus 5.5 | $0.00016 | $0.01116 |
| Sonnet 5.5 | $0.00008 | $0.00558 |
| Haiku 4.5 | $0.00004 | $0.00279 |
Grade A, and why
reliability-improvement-plan 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 1mo 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 — 310 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reliability Improvement Plan
Step 1: Gather context
Ask the user:
What workload would you like me to assess for reliability? Please share:
- Workload name and code packages/directories to analyze
- Availability target (99.9%, 99.95%, 99.99%, etc.)
- Recovery objectives (RTO and RPO if defined)
- Past incidents (optional — recent outages or near-misses)
If context is already provided or you are in a codebase with IaC, proceed directly.
Step 2: Fault Tolerance Discovery
Analyze infrastructure for single points of failure.
You MUST examine:
- Compute deployments (AZ distribution, instance count, ASG configs)
- Database configurations (Multi-AZ, read replicas, cluster topology)
- Cache configurations (cluster mode, replica counts, failover)
- Load balancer configurations (cross-zone, health checks, target groups)
- NAT Gateway placement (single vs per-AZ)
- DNS configurations (Route 53 health checks, failover routing)
- Queue and messaging configs (DLQ, redrive policies)
- Storage redundancy (S3 replication, EBS snapshots, EFS)
For each component, document:
- File path and line numbers
- Current redundancy level (single-AZ, multi-AZ, multi-region)
- Failure blast radius
- Failover mechanism (automatic, manual, none)
You MUST flag as HIGH RISK:
- Single-AZ database deployments for production workloads
- Compute without auto-scaling (fixed instance count)
- No health checks on load-balanced targets
- Single NAT Gateway serving multiple AZs
- Stateful services without replication
- Missing DLQ on async invocations (Lambda, SQS, EventBridge)
- No circuit breaker or timeout on external service calls
Step 3: Recovery Capability Discovery
Analyze backup and recovery configurations.
You MUST examine:
- AWS Backup plans and rules
- RDS automated backup settings (retention, PITR)
- S3 versioning and replication rules
- DynamoDB PITR and backup settings
- EBS snapshot configurations
- Cross-region replication rules
- Disaster recovery configurations (pilot light, warm standby resources)
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.
- 1mo ago First seen · 310 lines · 39 tokens per session scan A b22e710a2fb7
reliability-improvement-plan is a skill published in the GitHub repository Bilal140202/the-lord-of-the-skills (6 stars, last pushed 1mo ago), licensed MIT. It adds 39 tokens to every session and 2,790 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
serpsmith
Publish SEO articles, verify unattended health, and gate source-to-runtime releases.
tool-calling-tutor
Use when a tool-calling agent does not call a tool, sends wrong arguments, loops without stopping, or needs a function schema. Guides a four-branch diagnosis and five-step schema repair. Do not use for framework-specific, MCP-server, or production-observability questions.
ainb-fleet:daemons
Runtime-health view of the four fleet daemons — phone bridge, notifyd, ATC, and the fleet auto-continue daemon — in one table. Each row reports state (running / stopped / unknown), pid, uptime, last activity, error count, and a HEALTH reason that distinguishes a clean stop from a crash (stale heartbeat) or a…
ainb-fleet:atc
ATC (Air Traffic Control) — the single operator-visible fleet supervisor, in exactly one mode: lite (no LLM: deterministic scan, known-transient retry policy, safety caps, evidence) or full (the persistent orchestrating brain). Full mode is a plain ainb session (Claude or Codex) running a generated policy, woken on a…
ainb-fleet:fleet-needs
Workflow-backed Jarvis control panel. Runs the deterministic hangar workflow with verb=needs (discover → enrich → prioritize), renders the Jarvis HUD from its render-ready cards, fires AskUserQuestion per blocked session, and routes each answer back via tmux send-keys (broker fallback only). Requires the workflow gate…
first-plan-lens-mobile
Stack lens para mobile - React Native, Swift (iOS), Kotlin (Android), Flutter. Use durante Discovery quando pubspec.yaml, Package.swift, build.gradle.kts (Android) ou react-native em deps for detectado. Cobre navegação, estado, módulos nativos, build/distribuição.