What is prowler-docs?

A writing guide for Prowler documentation, including feature pages, tutorials, API references, and release notes. It sets rules for clear language, inclusive wording, terminology, and formatting.

Use it when writing or editing Prowler guides, tutorials, feature documentation, API references, or release notes.

It makes technical documentation easier to understand and keeps new pages consistent with the project’s standards.

prowler-docs — Skill by prowler-cloud

Install

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.

agentmods

npx agentmods add skills/prowler-cloud/prowler/prowler-docs

Any agent

npx skills add prowler-cloud/prowler --skill prowler-docs

Clone the repo

git clone --depth 1 https://github.com/prowler-cloud/prowler

Made for: Claude Code, Codex.

Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 771 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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	$0.00031	$0.00771
Opus 5	$0.00015	$0.00385
Sonnet 5	$0.00006	$0.00154
Haiku 4.5	$0.00003	$0.00077

Measured yesterday against content hash 3ee31ac65f7e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

prowler-docs 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 yesterday.

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.

skills/prowler-docs/SKILL.md · 125 lines

How it starts

The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.

When to Use

Use this skill when writing Prowler documentation for:

Feature documentation
API/SDK references
Tutorials and guides
Release notes

Brand Voice

Unbiased Communication

Avoid gendered pronouns (use "you/your" or "they/them")
Use inclusive alternatives: businessman → businessperson, mankind → humanity
No generalizations about gender, race, nationality, culture
Avoid militaristic language: fight → address, kill chain → cyberattack chain

Technical Terminology

Define key terms and acronyms on first use: "Identity and Access Management (IAM)"
Prefer verbal over nominal constructions: "The report was created" not "The creation of the report"
Use clear, accessible language; minimize jargon

Formatting Standards

Title Case Capitalization

Use Title Case for all headers:

Good: "How to Configure Security Scanning"
Bad: "How to configure security scanning"

Hyphenation

Prenominal position: "world-leading company"
Postnominal position: "features built in"

Bullet Points

Use when information can be logically divided:

Prowler CLI includes:
* **Industry standards:** CIS, NIST 800, NIST CSF
* **Regulatory compliance:** RBI, FedRAMP, PCI-DSS
* **Privacy frameworks:** GDPR, HIPAA, FFIEC

Interaction Verbs

Desktop: Click, Double-click, Right-click, Drag, Scroll
Touch: Tap, Double-tap, Press and hold, Swipe, Pinch

SEO Optimization

Sentence Structure

Place keywords at the beginning:

Good: "To create a custom role, open a terminal..."
Bad: "Open a terminal to create a custom role..."

Headers

H1: Primary (unique, descriptive)
H2-H6: Subheadings (logical hierarchy)
Include keywords naturally

MDX Components

Version Badge

import { VersionBadge } from "/snippets/version-badge.mdx"

## New Feature Name

<VersionBadge version="4.5.0" />

Description of the feature...

Warnings and Danger Calls

<Warning>
Disabling encryption may expose sensitive data to unauthorized access.
</Warning>

<Danger>
Running this command will **permanently delete all data**.
</Danger>

Read the full file on GitHub · 125 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

references/documentation-docs.md 355 B

Changes

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.

yesterday First seen · 125 lines · 31 tokens per session scan A 3ee31ac65f7e

Subscribe to this mod's changes

prowler-docs is a skill published in the GitHub repository prowler-cloud/prowler (14,718 stars, last pushed 3d ago), licensed Apache-2.0. It adds 31 tokens to every session and 771 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.

Git and workflow Learning and teaching Security aws hardening security-audit security-hardening security-tools

ponytail-sec-audit

Full project security audit. Scans the entire codebase across three passes: code that shouldn't exist, all dependencies assessed, all hardening findings. Produces a comprehensive numbered report with blast-radius narrative. Persists findings to .ponytail-sec/ for cross-scan tracking. For per-diff review use…

andypitcher/ponytail-sec · 74 tokens

ponytail-sec

Security companion for active development. Scopes to the current diff or changed files. Three passes: YAGNI code review, new-dep assessment, and up to 3 material hardening findings. Lean by design — surfaces the one thing to fix before merging, not a backlog. Use ponytail-sec-audit for a full project scan.