Prowler is an open-source cloud security platform that checks cloud environments for security issues and compliance with standards such as CIS, NIST, and GDPR. Security teams use it to assess configurations, prioritize findings, produce reports, and guide remediation.
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 prowler-cloud/prowler --skill prowler-readme-tablegit clone --depth 1 https://github.com/prowler-cloud/prowlerWrote 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/prowler-cloud/prowler/prowler-readme-table)<a href="https://agentmods.dev/skills/prowler-cloud/prowler/prowler-readme-table"><img src="https://agentmods.dev/badge/skills/prowler-cloud/prowler/prowler-readme-table/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/prowler-cloud/prowler/prowler-readme-table"><img src="https://agentmods.dev/badge/skills/prowler-cloud/prowler/prowler-readme-table.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00047 | $0.01041 |
| Opus 5 | $0.00023 | $0.00521 |
| Sonnet 5 | $0.00009 | $0.00208 |
| Haiku 4.5 | $0.00005 | $0.00104 |
Grade A, and why
prowler-readme-table 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 9d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to Use
Use this skill when updating the Prowler at a Glance table in the root README.md. This table tracks the number of checks, services, compliance frameworks, and categories for each supported provider.
Procedure
Step 1: Collect Stats via CLI
Run the following command for each provider and each metric:
python3 prowler-cli.py <provider> --list-<metric>
Providers: aws, azure, gcp, kubernetes, github, m365, oraclecloud, alibabacloud, cloudflare, mongodbatlas, openstack, nhn
Metrics: checks, services, compliance, categories
The CLI output ends with a summary line like:
There are 572 available checks.
There is 1 available Compliance Framework.
Extract the number from the summary line. Note that singular results use "There is" instead of "There are".
Step 2: Batch Extraction
Use this one-liner to collect all stats at once (handles both singular and plural output):
for provider in aws azure gcp kubernetes github m365 oraclecloud alibabacloud cloudflare mongodbatlas openstack nhn; do
for metric in checks services compliance categories; do
result=$(python3 prowler-cli.py $provider --list-$metric 2>&1 | sed -n 's/.*There \(are\|is\) .*\x1b\[33m\([0-9]*\)\x1b\[0m.*/\2/p')
echo "$provider $metric: $result"
done
done
Step 3: Update the Table
Edit the table in README.md (located in the # Prowler at a Glance section) with the collected numbers.
Table format:
| Provider | Checks | Services | [Compliance Frameworks](...) | [Categories](...) | Support | Interface |
|---|---|---|---|---|---|---|
| AWS | 572 | 83 | 41 | 17 | Official | UI, API, CLI |
Provider Name Mapping
| CLI Provider | Table Display Name |
|---|---|
aws |
AWS |
azure |
Azure |
gcp |
GCP |
kubernetes |
Kubernetes |
github |
GitHub |
m365 |
M365 |
oraclecloud |
OCI |
alibabacloud |
Alibaba Cloud |
cloudflare |
Cloudflare |
mongodbatlas |
MongoDB Atlas |
openstack |
OpenStack |
nhn |
NHN |
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.
- 9d ago First seen · 111 lines · 47 tokens per session scan A bf645f014e16
prowler-readme-table is a skill published in the GitHub repository prowler-cloud/prowler (14,767 stars, last pushed yesterday), licensed Apache-2.0. It adds 47 tokens to every session and 1,041 once invoked, about $0.0002 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-30.
Other skills, from other repositories
performing-aws-account-enumeration-with-scout-suite
Perform comprehensive security posture assessment of AWS accounts using ScoutSuite to enumerate resources, identify misconfigurations, and generate actionable security reports.
contract-key-safety
Trigger Pattern Always required for DAML audits (self-skips if no template defines a key) - Inject Into Breadth agents, depth-state-trace.
Cloud Security & Container Hardening
AWS/Azure/GCP security auditing, container and Kubernetes hardening, Infrastructure as Code scanning, and cloud compliance assessment.
eks-operation-review
Comprehensive Amazon EKS operational review aligned with the AWS EKS Best Practices Guide. Use this skill when a user asks to review, audit, or assess EKS clusters for best practices compliance, operational readiness, security posture, cost optimization, reliability, networking, scalability, or upgrade readiness.…
rds-operation-review
Comprehensive Amazon RDS and Aurora operational review aligned with the AWS Well-Architected Framework and RDS/Aurora best practices. Use this skill when a user asks to review, audit, or assess RDS instances or Aurora clusters for best practices compliance, security posture, reliability, performance, cost…
cis-aws-database-3.11
Ensure to Regularly Review Security Configuration.