T09 · Insecure Skill Coding Practices
- Location
SKILL.md:330- Finding
State-Changing Module Power Commands Conflict with Read-Only Safety Classification
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is mostly a read-only Cisco health-check guide, but it includes device state-changing and potentially service-disrupting NX-OS commands despite declaring itself read-only.
Review before installing. Use this skill only for diagnostic collection unless your workflow blocks or requires explicit human approval for `switchto vdc`, `poweroff module`, and `no poweroff module`. Treat crash and core data as sensitive and follow your organization's handling and change-control process.
SKILL.md:330State-Changing Module Power Commands Conflict with Read-Only Safety Classification
The skill includes guidance to power-cycle NX-OS modules using poweroff module [n] / no poweroff module [n], which is an explicitly disruptive administrative action. In a skill presented as health-check or triage guidance, including such commands without strong segregation or safeguards creates a real risk of service interruption if an agent or operator follows them directly.
The skill is labeled read-only, but it explicitly instructs the operator to run switchto vdc [name], which changes operational context on the device. Even if this is not a configuration change, it is a state-changing action that can mislead an agent or user into taking actions outside the promised safety boundary and increase the chance of follow-on commands being executed in the wrong VDC.
The skill mixes VDC switching and module power-cycling guidance into troubleshooting sections without a prominent warning that these actions can change device state or interrupt service. Because the surrounding content is framed as routine health-check guidance, users or agents may treat these steps as safe defaults rather than elevated-risk operations.
The skill directs collection of crashinfo, core dumps, and exception logs but does not warn that these artifacts can contain sensitive operational details, memory contents, topology, credentials, or configuration fragments. In troubleshooting contexts these files are commonly exported or shared, so missing handling guidance increases the risk of inadvertent data exposure.
Line L004 states that all commands are "read-only (show/display only)," which narrowly describes show/display commands only. However, the reference later includes dir crashinfo: as part of crash-data inspection, which is still read-only but is not a show/display command, so the documentation actively overstates the exact command class used.
No suspicious patterns detected.