steady-state-sidecar-sync-de7e9e — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited steady-state-sidecar-sync-de7e9e (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Domain: extensions-mcp Trigger: Use when a derived cache or mirror can disappear between runs even though the primary installation state did not change this time. Source Pattern: Distilled from reviewed authoritative-state to sidecar-cache synchronization flows.
Rebuild sidecar or mirror caches from authoritative state after reconciliation settles, even when the primary changed signal is false. Ephemeral environments often lose derived artifacts while retaining the main installed set, so gating sidecar sync only on new installs leaves fresh processes under-provisioned. Keep the sync idempotent and conceptually separate from the main change signal.
If worker nodes derive a local metadata mirror from the installed extension registry, rebuild that mirror on each boot even when no extension was newly installed.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.