List compliance extension packs and their status.
/extensions list
pack_id before running /extensions enable/extensions list
What you’ll see: a table of every pack on disk with its status, version, restrictiveness, source, and enable date — followed by a totals footer like 4 packs available · 2 enabled · 0 waivers active.
/extensions list # the one and only form — no arguments
extensions/, the plugin install (if present), or the compiled bundle install at .claude/extensions-installed/, in that order.<domain>/<name>) and reads each pack’s version, source, and restrictiveness..claude/extensions/.enabled.json to mark each pack enabled or disabled. If the file doesn’t exist, all packs show as disabled — that just means nothing is opted in yet.compliance/hipaa disabled 1.0.0 5 original —| Problem | Fix |
|---|---|
No extension packs installed |
Add packs under extensions/<domain>/<name>/, or install a bundle that ships packs |
All packs show disabled even though some should be enabled |
Install jq — without it, the tool cannot read .enabled.json and assumes no packs are enabled |
A pack shows ? for version/restrictiveness |
That pack’s opt-in frontmatter is malformed or missing required fields (version, source, restrictiveness) — the listing continues, but fix the pack before enabling it |