ddos-guardian SKILL.md skillA
ddos-guardian from aws-samples/sample-ddos-guardian-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add aws-samples/sample-ddos-guardian-skills/ddos-guardian@git:20260909.a91dca2Pins git:20260909.a91dca2 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- aws-samples/sample-ddos-guardian-skills
- Path
skills/ddos-guardian/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260909.a91dca2, committed Sep 9, 2026
- First version recorded
- Sep 4, 2026
- Size
- 33,405 bytes
- Repository stars
- 3
- License
- MIT-0
Reviews an AWS WAFv2 web ACL (ALB, CloudFront, API Gateway, AppSync) against AWS best practices, writing a self-contained HTML report: severity-rated findings, remediation, cost and WCU. Use it even when nobody says "WAF": what is wrong with my web ACL, review or harden it, here is a get-web-acl export or any file with WebACL/web_acl rules, customers are blocked, find the culprit rule and a safe exception, am I protected against L7 DDoS, bots, scraping, scripted signups or credential stuffing…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# DDoS Guardian — AWS WAF rules assessment A WAF review fails in two directions. Report a problem that is not real and the customer stops trusting everything else in the document. Miss a real one and they stay exposed. Both come from the same root cause: judging a configuration without the facts needed to judge it. So the work is split. `waf-assess.py` decides everything decidable from the config text and writes those findings itself. What is left is either judgment about intent — which no script should fake — or a fact only an operator has. You gather the facts, verify the machine's claims, reason about the rest, and `waf-report.py` renders it. ## Language **All output is English.** Write the report, findings and headings in English regardless of the language of the user's message. ## Pipeline ``` waf-assess.py → ask for context → waf-assess.py again → YOU write findings → waf-report.py ``` `waf-assess.py` writes most of the findings. Your job is to adopt those, resolve the context that changes them, then cover only the sections it could not decide. ## Deliverables 1. **`waf-assessment-report.html`** — one self-contained file, no external CSS, JS, fonts …
Read the whole file at its exact version.
How to install
mdr add aws-samples/sample-ddos-guardian-skills/ddos-guardian@sha256:935c3ae6289bf2ccThe line at the top of this page pins the label git:20260909.a91dca2, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_4eheyxifdydp6wuo)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Sep 4, 2026 and Sep 9, 2026, about one every 5 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260909.a91dca2 latest | 2026-09-09 | a91dca2 | 33,405 B | A | view · diff |
| git:20260904.c8929a7 | 2026-09-04 | c8929a7 | 33,783 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (33405 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
aws-samples/sample-ddos-guardian-skills · 3 stars · license MIT-0 · pushed 2026-09-09 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_4eheyxifdydp6wuo GET https://markdownregistry.com/api/v1/resolve?ref=aws-samples/sample-ddos-guardian-skills/ddos-guardian GET https://markdownregistry.com/api/v1/blob/935c3ae6289bf2cc1403c662e7a9c9d020440fb300819f62006705f69505870f
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.