Aegis Gateway Diagnostics — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited Aegis Gateway Diagnostics (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.
Aggregate score unchanged between these scans.
The primary manifest — the file an agent reads to learn what this artifact does.
Be precise about the failing layer. "Gateway connected" is not the same as "planner can call a tool-ready local worker".
aegis_mcp_status.aegis_gateway_status.aegis_gateway_accounts.aegis_gateway_deliveries when queue or channelreply behavior is involved.
aegis_board and reports before recommending a fix.
Use these labels in the answer:
mcp_unavailable: Codex cannot see the Aegis MCP server.auth_or_owner_scope: MCP/server responds but token or owner/profile scope is wrong.server_side_ready: server-side tools can act even if local worker cannot.gateway_account_unhealthy: platform account/binding/delivery health issue.worker_connected_not_tool_ready: a worker heartbeat exists but declaredtools/tool schemas are absent.
worker_tool_ready: local execution path exists; failures need job evidence.provider_planner_missing: AI planning provider is not configured or failed.Return: observed state, most likely layer, evidence, and one next operational check. Do not say Aegis has no tools when only one runtime path is missing.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.