cortex-logs — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited cortex-logs (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.
Show recent cortex service logs. These are the binary's stdout/stderr, not syslog entries received from clients. Use the cortex MCP tool with action=tail for received log entries.
echo "$CLAUDE_PLUGIN_OPTION_IS_SERVER"If false, explain that the local plugin is in client mode and has no local service logs to tail.
100: that many lines, no follow--follow or -f: last 50 lines, then stream CORTEX_HOME="${CORTEX_HOME:-$HOME/.cortex}"
docker compose --env-file "${CORTEX_HOME}/.env" -f "${CORTEX_HOME}/compose/docker-compose.yml" logs cortex --tail <N> --no-colorFor follow mode, add -f and omit --no-color.
If the plugin compose project has no container, report that Docker mode is configured but no plugin-managed container is running. Do not guess a source checkout path.
Show the captured logs directly. If follow mode is active, the streaming output is the deliverable until the user interrupts.
If the logs show obvious unhealthy patterns such as repeated restarts, panics, bind errors, or DB lock errors, summarize the pattern after the log excerpt and suggest cortex-dr for full diagnostics.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.