control-os — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited control-os (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.
The sanctioned "motor cortex" for the host: act through systemd / logind / journald / D-Bus, not raw PID hacks.
Full tool inventory (22):
os_diag, os_services, os_journal, os_resources, os_processes, os_pressure, os_net, os_disk, os_hardware, os_containers, os_sensors, os_session, os_verifyos_service, os_power, os_dbus, os_time, os_hostname, os_locale, os_notifyos_wait, os_reloados_diag (health, privilege, backends) → observe with os_services / os_journal / os_resources / os_processes / os_pressure / os_net / os_disk / os_hardware / os_containers / os_sensors / os_session. Understand state before changing it.os_service (start/stop/restart/enable/…), os_power (suspend/reboot/poweroff), os_dbus / os_time / os_hostname / os_locale / os_notify.os_wait and/or re-run os_services unit=… / os_journal unit=… — don't assume the action took.dbus, systemd-logind, sshd, NetworkManager/networkd, tailscaled, the user@… session, goosed, etc. — is REFUSED. This stops you cutting off your own bus / login / network / remote access. If you genuinely mean it, pass force=true. (start/enable/reload are never blocked.)os_power is irreversible/disruptive → refused unless `confirm=true`. State what you're about to do, then call with confirm=true.os_dbus op=call has side effects → needs force=true. list/tree/introspect are free.Read-only tools work unprivileged. System-scope mutations (os_service on system units, os_power) need root or polkit — when not root the server tries sudo -n; if that's not set up it tells you plainly. Options: run goosed/the server as root, add passwordless sudo for systemctl, or a polkit rule. scope="user" manages the user's own units with no root.
os_services unit=foo.service (state/last result) → os_journal unit=foo.service priority=err lines=80 → fix → os_service unit=foo.service action=restart → confirm.os_resources → os_processes by=cpu (or by=mem) → act.os_services state=failed to list everything broken at once.os_notify summary="build done" urgency=normal.Pairs with screen-mcp (GUI eyes+hands), NATS (messaging), and A2A (inter-agent) for a full-stack agent: sense the kernel/services, act on the system, drive the desktop, coordinate the fleet.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.