omarchy-plugin-audit

Compare installed Omarchy plugin commits against marketplace-validated commits.

3|Updated Sep 12, 2026
One-click install
npx skills add https://github.com/mtolhuys/omakit --skill omarchy-plugin-audit-mtolhuys
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: omarchy-plugin-audit
Source: https://github.com/mtolhuys/omakit/tree/main/skills/omarchy-plugin-audit
Command: npx skills add https://github.com/mtolhuys/omakit --skill omarchy-plugin-audit-mtolhuys

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Installed third-party Omarchy plugins can silently drift from the exact commits the marketplace reviewed, leaving you running code that was never validated. This Skill audits installed plugins against the marketplace catalog so you know precisely which plugins match a validated commit and which do not. ## Core Features & Use Cases - Commit Comparison: Classifies each installed plugin as validated, ahead, diverged, unverified, unlisted, or unknown by reading the shell's installed list, the marketplace catalog, and local Git facts. - Stacking Flags: Reports modified, disabled, and upstream-moved flags alongside the primary state without collapsing them together. - Structured Output: Supports --json for machine-readable documents, --offline to use the pinned catalog, and --drift as a view filter. - Use Case: Before enabling or updating a third-party plugin, run the audit to confirm its installed HEAD matches a marketplace-validated commit, and get the exact checkout command if it has drifted. ## Quick Start Ask the assistant to audit my installed Omarchy plugins and tell me which ones are running commits the marketplace never validated.

Frequently Asked Questions about omarchy-plugin-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check if installed Omarchy plugins match marketplace review?▼

Run omakit audit to compare every installed third-party plugin's HEAD commit against the commits the marketplace records as validated. Use omakit audit <plugin-id-or-dir> to scope the check to a single plugin.

What do the omakit audit states validated, ahead, and diverged mean?▼

Validated means installed HEAD is a marketplace-validated commit. Ahead means a validated commit is an ancestor but HEAD has later unvalidated commits. Diverged means installed history does not descend from a validated commit or the origin differs.

Does omakit audit modify my installed plugins?▼

No, the audit is read-only. It reads the shell's installed list, the marketplace catalog, and local Git facts without changing either checkout, and it never runs the printed checkout command without your explicit request.

Can I run the plugin audit without network access?▼

Yes, use the --offline flag so the live marketplace catalog is not read. The report header will name the catalog pin used for the comparison instead.

Why does omakit audit report NOT AUDITED with exit code 1?▼

NOT AUDITED appears when a row is unknown because Git or the source directory could not answer, so it could not be compared. An unknown row is counted apart from drift, and the closing sentence states why.

Should I use omarchy plugin update to fix a diverged plugin?▼

No, update moves to a mutable HEAD and does not establish marketplace validation. The audit prints the exact checkout command for the validated commit and names the marketplace form for validating a newer one.