Security checks for vulnerabilities and agentic risk
Overview
This server-operations skill is mostly coherent, but some troubleshooting recipes present high-impact system changes as direct commands without enough local safeguards.
Review before installing if you expect the agent to operate on production systems. Keep it to read-only diagnostics by default, require explicit approval for every state-changing command, and do not run the troubleshooting-guide remediation snippets until paths, services, backups, rollback steps, and environment-specific managers such as firewall and DNS tooling have been verified.
# Line 219
iptables -A INPUT -p tcp --dport port -j ACCEPT
bash
# Line 223
echo "nameserver 8.8.8.8" > /etc/resolv.conf
bash
# Line 268
find /tmp -type f -mtime +7 -delete
bash
# Line 371
fsck /dev/sda1
bash
# Line 665
echo -1000 > /proc/$(pidof mysql)/oom_score_adj
Technical Analysis
The troubleshooting guide presents commands that directly alter kernel state, firewall policy, DNS configuration, filesystem contents, filesystem metadata, and Out-of-Memory Killer behavior. These operations generally require root or equivalent administrative privileges.
Although the Skill contains general safety principles elsewhere, the affected recipes do not place immediate safeguards around these commands. In particular:
Dropping kernel caches can produce substantial I/O load and performance disruption without resolving the underlying memory problem.
Appending an unrestricted firewall acceptance rule can expose a service on every applicable interface and source network.
Overwriting /etc/resolv.conf destroys the existing DNS configuration and may conflict with NetworkManager, systemd-resolved, DHCP, or local resolver settings.
Deleting every regular file in /tmp older than seven days can remove files still required by applications or users.
Running fsck against a mounted or active filesystem can cause corruption or data loss.
Assigning MySQL an OOM adjustment of -1000 makes it effectively exempt from OOM termination, potentially causing the kernel to terminate other critical processes or destabilize the h
...[truncated 2018 chars]
Remediation
View remediation
Remediation Suggestions
Require explicit, command-specific user authorization immediately before every state-changing or privileged operation.
Separate diagnosis from remediation. Default to read-only commands and provide proposed changes for review rather than executing them automatically.
Replace cache-dropping advice with root-cause analysis using free, vmstat, sar, pressure-stall information, process memory metrics, and application-specific profiling.
Before changing firewall policy:
Identify the required interface, source CIDR, protocol, and destination port.
Display the current ruleset.
Prefer a narrowly scoped rule.
Define and test a rollback command.
Confirm that the change will not expose the service publicly.
Never overwrite /etc/resolv.conf directly without detecting its manager. Back up the existing configuration and modify NetworkManager, systemd-resolved, DHCP, or the platform-specific resolver configuration through its supported interface.
Replace direct temporary-file deletion with a preview:
bash
find /tmp -xdev -type f -mtime +7 -print
Review ownership and active use before removal, and prefer the operating system's temporary-file management mechanism.
Before fsck, identify the filesystem and backing device, verify backups, confirm it is unmounted, enter an appropriate maintenance environment, and use non-modifying inspection mode first where supported.
Do not set oom_score_adj to -1000 as a generic fix. Correct the memory shortage, apply service-level memory limits, and document the consequences of any OOM policy adjustment.
Add local warnings, prerequisite checks, expected effects, verification steps, and tested rollback instructions next to every high-impact command instead of relying only on general safety text elsewhere in the Skill.
The guide recommends overwriting critical network configuration (for example replacing /etc/resolv.conf) and modifying firewall rules with direct commands, without strong warnings about persistence, environment differences, or lockout risk. In the context of an operational agent skill, these instructions are more dangerous because they can break connectivity, bypass change controls, or weaken host/network security if followed verbatim.
Content
No source excerpt is available for this finding.
Missing User Warnings
High
Category
Not specified by scanner
Confidence
97% confidence
Finding
This section contains irreversible cleanup commands such as truncating logs and deleting files from /tmp, but it does not provide prominent safeguards around data retention, forensic value, service impact, or path validation. In a troubleshooting skill, operators may execute these commands during incidents, which can destroy evidence, remove needed data, or interrupt running services.
Content
No source excerpt is available for this finding.
Natural-Language Policy Violations
Medium
Category
Not specified by scanner
Confidence
88% confidence
Finding
The skill name and all user-facing instructions are presented only in Chinese, indicating a language-specific experience, but the file does not state that this is optional or limited to Chinese-speaking users. Under the policy, forcing a specific language without user opt-in is a natural-language policy violation.
Content
No source excerpt is available for this finding.
Vague Triggers
Medium
Category
Not specified by scanner
Confidence
91% confidence
Finding
The activation condition says the skill applies when the user requests server maintenance, system diagnosis, performance optimization, fault repair, or routine operations, which is a very wide scope with no exclusion conditions or explicit trigger phrases. This makes it unclear when the skill should activate versus when a more specialized skill should handle the request.
Content
No source excerpt is available for this finding.
Natural-Language Policy Violations
Medium
Category
Not specified by scanner
Confidence
92% confidence
Finding
The title and all instructional content are presented only in Chinese, which can amount to a language-policy violation when users are not given an opt-in or alternative locale. The file does not state that it is intended only for a Chinese-speaking or region-specific audience, nor does it provide a language selection mechanism.
Content
No source excerpt is available for this finding.
Session Persistence
Medium
Category
Rogue Agent
Confidence
80% confidence
Finding
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
Content
Scanner excerpt · references/linux-commands.md (reported line 129)May include surrounding context.
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
Content
Scanner excerpt · references/linux-commands.md (reported line 417)May include surrounding context.
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
Content
Scanner excerpt · references/safety-checklist.md (reported line 93)May include surrounding context.
This section includes state-changing remediation commands such as killing processes and writing to /proc/sys/vm/drop_caches, but the guide does not prominently warn about privilege requirements, operational impact, or rollback considerations. In an agent skill for server operations, such commands may be surfaced or copied into production environments, increasing the chance of accidental service disruption or loss of diagnostic state.
Content
No source excerpt is available for this finding.
Sudo/Root Execution
Medium
Category
Privilege Escalation
Confidence
80% confidence
Finding
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
Content
Scanner excerpt · references/troubleshooting-guide.md (reported line 158)May include surrounding context.
The header comments explicitly characterize the script as using only read-only operations with no destructive side effects. In practice, lines L291-L293 write the generated report to a file path supplied by the caller, which contradicts the documented '只读操作' claim.
Content
No source excerpt is available for this finding.
Missing User Warnings
Medium
Category
Not specified by scanner
Confidence
90% confidence
Finding
The script gathers system inventory details such as OS version, kernel, CPU, memory, disks, load, and process count, and can persist them to disk without clearly warning users about the sensitivity of that data. In an ops skill context this is expected functionality, but the lack of disclosure and minimization can still expose environmental details useful for fingerprinting or later attacks if the report is shared or stored insecurely.
Content
No source excerpt is available for this finding.
Description-Behavior Mismatch
Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding
The help text and header describe the script as safely collecting basic system information for diagnostics, emphasizing read-only and non-destructive behavior. However, the --output option and file redirection later in the script persist the data to a user-specified file, which is a write side effect beyond purely read-only collection.