arthai-marketplace

/extensions list

List compliance extension packs and their status.

Synopsis

/extensions list

When to use it

Quickstart

/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.

Examples

/extensions list    # the one and only form — no arguments

What it does

  1. Resolves the extension root — project extensions/, the plugin install (if present), or the compiled bundle install at .claude/extensions-installed/, in that order.
  2. Enumerates packs on disk (organized as <domain>/<name>) and reads each pack’s version, source, and restrictiveness.
  3. Cross-references the project’s .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.
  4. Prints the table and a one-line footer with totals (packs available, enabled, active waivers).

Output & artifacts

Troubleshooting

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