Skip to content

elliewlh2094/codex-robotics-skills / .agents/skills/robotics-security

robotics-security

Flagged

Security hardening for robotic systems where cyber failures can create physical risk. Use when securing ROS2 or DDS communications, configuring SROS2 encryption and access control, hardening robot computers, managing certificates, credentials, firewalls, secure boot, network segmentation, robot fleet security, e-stop isolation, safety controller isolation, or IEC 62443-oriented robotics security.

Security report

Flagged

Static analysis of one exact version. It reduces risk and shows evidence; it does not certify that a skill is safe.

Commit
bcf6b41f8dd280194e280955068e3d8e18715bdb
Content hash
c9ca581793130bf6c91ee881c59d856944b0bad80da3e496256d79a8a924c5e4
Scanned
2026-11-17
Scanner version
skillxone-scan-1.0.0
Policy version
0.1-draft
Decision
2 open critical or high findings.
Verification expires
Not applicable

Findings (2 high, 2 medium, 7 low)

  • highCMD-HISTORY-LOG-WIPESKILL.md:413

    Shell history or system logs are erased, which hides what was done.

    0 3 1 * * root /opt/robot/scripts/rotate_certs.sh >> /var/log/cert-rotation.log 2>&1

    Suggested fix: Remove commands that clear history or logs.

    Report as false positive

  • highFILE-SSH-KEYSSKILL.md:736

    The skill refers to SSH keys, a location that holds private data or credentials.

    -w /home/robot-admin/.ssh/ -p wa -k ssh_keys

    Suggested fix: Do not read credential stores or private files. If the task needs a credential, ask the user to provide it through the environment.

    Report as false positive

  • mediumCMD-PERSISTENCESKILL.md:319

    The skill sets something to run automatically later (scheduled task, login item or shell start-up file).

    sudo apt install fail2ban -y && sudo systemctl enable --now fail2ban

    Suggested fix: Do not install persistent jobs or edit shell start-up files. Tell the user what to add if they want it.

    Report as false positive

  • mediumCRED-GENERIC-SECRETSKILL.md:348

    A value assigned to a secret-like name looks like a real credential rather than a placeholder.

    self.api_key = "sk-l…[redacted]"

    Suggested fix: If this is a real secret, revoke it and load it from the environment. If it is an example, make that obvious (for example "your-api-key").

    Report as false positive

  • lowCMD-SUDOSKILL.md:298

    A command runs with administrator privileges.

    sudo systemctl restart sshd

    Suggested fix: Avoid sudo where possible. If it is required, explain why so the user can decide.

    Report as false positive

  • lowCMD-SUDOSKILL.md:319

    A command runs with administrator privileges.

    sudo apt install fail2ban -y && sudo systemctl enable --now fail2ban

    Suggested fix: Avoid sudo where possible. If it is required, explain why so the user can decide.

    Report as false positive

  • lowCMD-SUDOSKILL.md:326

    A command runs with administrator privileges.

    sudo dpkg-reconfigure -plow unattended-upgrades

    Suggested fix: Avoid sudo where possible. If it is required, explain why so the user can decide.

    Report as false positive

  • lowCMD-SUDOSKILL.md:391

    A command runs with administrator privileges.

    sudo chown root:robot /etc/robot/secrets.env

    Suggested fix: Avoid sudo where possible. If it is required, explain why so the user can decide.

    Report as false positive

  • lowCMD-SUDOSKILL.md:420

    A command runs with administrator privileges.

    sudo find /opt/robot/sros2_keystore -type d -exec chmod 750 {} \;

    Suggested fix: Avoid sudo where possible. If it is required, explain why so the user can decide.

    Report as false positive

  • lowCMD-SUDOSKILL.md:794

    A command runs with administrator privileges.

    sudo ros2 launch my_robot bringup.launch.py

    Suggested fix: Avoid sudo where possible. If it is required, explain why so the user can decide.

    Report as false positive

  • lowCMD-SUDOSKILL.md:801

    A command runs with administrator privileges.

    sudo -u robot ros2 launch my_robot bringup.launch.py

    Suggested fix: Avoid sudo where possible. If it is required, explain why so the user can decide.

    Report as false positive

Checks run

  • prompt-injection
  • dangerous-commands
  • credentials
  • network
  • file-access
  • integrity

Checks skipped

  • dependencies: No dependency manifest in the skill directory.
  • gitleaks: gitleaks is not installed on this host.
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall