Prompt Audits

Introduction

A prompt audit reviews a system's prompts for security, quality, cost, and compliance. Common engagement type.

Beginner analogy: Like a code audit — structured checklist, written report.

Understanding the topic

Core concepts to understand:

• Checklist: role, format, refusals, delimiters, sensitive data, eval coverage.
• Score each item; flag risks.
• Cost analysis — where is money burned?
• Quality analysis — eval coverage, hallucination rate.
• Written report with prioritised fixes.

Syntax reference

Visual workflow / architecture:

Inputs: prompts + logs + evals
  ▼ checklist scoring
  ▼ cost + quality analysis
  ▼ prioritised fixes report

Real-world use

Prompt audits are sold by consultancies; junior engineers do them internally too.

Best practices

• Templatise the checklist.
• Bring receipts (cost / eval numbers).
• Prioritise by impact & effort.

Hands-on exercise

Interview preparation — practice these questions:

• Q1. Walk through an audit you've done.
• Q2. Checklist items?
• Q3. Prioritisation framework?
• Q4. Report format?