Back to skill

Security audit

linux-performance-analyzer

Security checks for vulnerabilities and agentic risk

Overview

This appears to be a legitimate Linux performance-tuning skill, but it needs review because it can guide broad root-level, persistent system changes without consistently strong safeguards.

Install only for use by experienced Linux administrators. Keep diagnosis read-only by default, require explicit approval before any root or persistent command, test changes outside production first, record current values and backups, protect snapshot and heap-dump outputs as sensitive, and review every /etc, systemd, crontab, /proc, and /sys change before execution.

Vulnerability Patterns
  • System PersistenceInstalls backdoors, hooks, services, or scheduled tasks that survive the run
  • Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
Findings (4)

T06 · System Persistence

Error
Location
references/cpu.md:95
Finding
Persistent Privileged System Tuning Without Sufficient Safety Controls<![CDATA[ ## Vulnerability Details **File Locations**: - `references/cpu.md:95-108` - `references/memory.md:144-158` - `references/disk_io.md:76-83` - `references/disk_io.md:109-113` - `references/disk_io.md:254-255` - `references/disk_io.md:314-318` - `SKILL.md:315-321` - `SKILL.md:357-361` **Vulnerability Type**: Persistent privileged system modification **Risk Level**: High ### Vulnerable Code CPU governor service: ```bash cat > /etc/systemd/system/cpu-performance.service << 'EOF' [Unit] Description=Set CPU governor to performance After=multi-user.target [Service] Type=oneshot ExecStart=/bin/bash -c "for f in /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor; do echo performance > $f; done" RemainAfterExit=yes [Install] WantedBy=multi-user.target EOF systemctl enable --now cpu-performance.service ``` Transparent Huge Pages service: ```bash cat > /etc/systemd/system/disable-thp.service << 'EOF' [Unit] Description=Disable Transparent Huge Pages After=network.target [Service] Type=oneshot ExecStart=/bin/sh -c "echo never > /sys/kernel/mm/transparent_hugepage/enabled" ExecStart=/bin/sh -c "echo never > /sys/kernel/mm/transparent_hugepage/defrag" RemainAfterExit=yes [Install] WantedBy=multi-user.target EOF systemctl enable --now disable-thp.service ``` Persistent I/O scheduler rule: ```bash cat > /etc/udev/rules.d/60-ioscheduler.rules << 'EOF' # NVMe SSD ACTION=="add|change", KERNEL=="nvme[0-9]*", ATTR{queue/scheduler}="none" # SATA SSD ACTION=="add|change", KERNEL=="sd[a-z]", ATTR{queue/rotational}=="0", ATTR{queue/scheduler}="mq-deadline" # HDD ACTION=="add|change", KERNEL=="sd[a-z]", ATTR{queue/rotational}=="1", ATTR{queue/scheduler}="bfq" EOF udevadm control --reload-rules && udevadm trigger ``` Boot script replacement: ```bash cat > /etc/rc.local << 'EOF' #!/bin/bash blockdev --setra 4096 /dev/sda EOF chmod +x /etc/rc.local ``` Recurring disk tasks: ```bash systemctl enable fstrim.timer systemctl start fstrim.timer ``` ```bash systemctl ena ...[truncated 2513 chars]
Remediation
<![CDATA[ ## Remediation Suggestions 1. Make read-only diagnosis the default behavior. 2. Require explicit, informed user approval immediately before every privileged or persistent operation. 3. Apply temporary settings first and observe them for a defined period before offering persistence. 4. Record the actual current values rather than assuming distribution defaults. 5. Never replace shared files such as `/etc/rc.local`; use a dedicated, narrowly scoped systemd unit or configuration drop-in. 6. Back up every modified file with ownership, mode, and timestamp preservation. 7. Validate the target device, kernel parameter, available scheduler, CPU governor, and service name before modification. 8. Provide complete rollback commands, including: - `systemctl disable --now <unit>` - Removal of the created unit. - `systemctl daemon-reload` - Removal or restoration of cron, udev, sysctl, and module-load entries. - Restoration of all captured runtime values. 9. Avoid appending duplicate entries to shared configuration files. 10. Add a dry-run mode that displays proposed changes and their scope without executing them. ]]>

T09 · Insecure Skill Coding Practices

Error
Location
scripts/perf_monitor.sh:13
Finding
Predictable Symlink-Following Log Files in a Shared Temporary Directory<![CDATA[ ## Vulnerability Details **File Location**: `scripts/perf_monitor.sh:13-14, 24-32` **Vulnerability Type**: Insecure temporary-file handling and symlink attack **Risk Level**: High when executed with elevated privileges ### Vulnerable Code ```bash INTERVAL=5 # Sampling interval in seconds LOG_FILE="/tmp/perf_monitor_$(date +%Y%m%d_%H%M%S).log" ALERT_LOG="/tmp/perf_alerts_$(date +%Y%m%d).log" log() { echo "[$(date '+%Y-%m-%d %H:%M:%S')] $1" | tee -a "$LOG_FILE" } alert() { local msg="⚠️ ALERT: $1" echo "[$(date '+%Y-%m-%d %H:%M:%S')] $msg" | tee -a "$LOG_FILE" >> "$ALERT_LOG" } ``` ### Technical Analysis The monitor creates log paths directly under the globally writable `/tmp` directory. The daily alert filename is completely predictable, while the main filename is predictable to the second. The files are opened in append mode without exclusive creation, ownership validation, symlink rejection, or a private parent directory. Shell redirection and `tee -a` normally follow symbolic links. If the script is run as root, a local attacker can pre-create one of these paths as a symbolic link to a root-writable target. The monitor will then append its output to that target using the monitor's privileges. File confidentiality is also dependent on the caller's `umask`; the script does not enforce mode `0600`. ### Attack Path 1. A local unprivileged attacker determines the current date. 2. The attacker creates a symbolic link such as: ```bash ln -s /path/to/root-owned-target /tmp/perf_alerts_YYYYMMDD.log ``` 3. An administrator starts `perf_monitor.sh` as root. 4. A monitored metric crosses a configured threshold. 5. The shell opens the predictable alert path and follows the attacker's symbolic link. 6. Root-privileged monitoring text is appended to the chosen file. The attacker does not directly control the full appended text, so reliable arbitrary command execution is not established. However, arbitrary root-owned file co ...[truncated 654 chars]
Remediation
<![CDATA[ ## Remediation Suggestions 1. Set a restrictive umask at startup: ```bash umask 077 ``` 2. Create a private directory using `mktemp -d`: ```bash LOG_DIR=$(mktemp -d "${TMPDIR:-/tmp}/perf-monitor.XXXXXX") || exit 1 LOG_FILE="$LOG_DIR/monitor.log" ALERT_LOG="$LOG_DIR/alerts.log" ``` 3. Verify that the directory is owned by the current effective user and is not a symlink. 4. Create files exclusively and reject existing paths. 5. Add a cleanup trap where temporary retention is not required. 6. For durable monitoring, write to a dedicated directory under `/var/log` created by installation code with explicit ownership and mode. 7. Run the monitor under a dedicated unprivileged account rather than root. 8. Prevent concurrent instances from sharing a log path, for example by using a securely created lock file. ]]>

T09 · Insecure Skill Coding Practices

Error
Location
references/disk_io.md:150
Finding
Unsafe Generic Disk, Memory, and Scheduling Tuning Examples<![CDATA[ ## Vulnerability Details **File Locations**: - `references/disk_io.md:150-156` - `references/disk_io.md:203-231` - `references/memory.md:92-107` - `references/memory.md:231-253` - `references/cpu.md:119-130` **Vulnerability Type**: Potentially destructive privileged operational guidance **Risk Level**: High ### Vulnerable Code Unsafe filesystem mount example: ```bash # ext4 optimization mount options # /etc/fstab example: # /dev/sdb1 /data ext4 noatime,nodiratime,data=writeback,barrier=0 0 2 # noatime: disable access-time recording # nodiratime: disable directory access times # data=writeback: writeback mode, offering performance but possible inconsistency after power loss # barrier=0: disable write barriers; data loss is possible ``` Fixed-path disk benchmarks and cleanup: ```bash # Sequential read test fio --name=seq-read --ioengine=libaio --iodepth=32 \ --rw=read --bs=1M --size=4G --numjobs=1 \ --filename=/data/fio_test --direct=1 \ --runtime=30 --time_based --group_reporting # Random read test fio --name=rand-read --ioengine=libaio --iodepth=64 \ --rw=randread --bs=4k --size=4G --numjobs=4 \ --filename=/data/fio_test --direct=1 \ --runtime=30 --time_based --group_reporting # Mixed read/write test fio --name=mixed-rw --ioengine=libaio --iodepth=32 \ --rw=randrw --rwmixread=70 --bs=4k --size=4G --numjobs=4 \ --filename=/data/fio_test --direct=1 \ --runtime=30 --time_based --group_reporting # Remove test file rm /data/fio_test ``` OOM immunity: ```bash cat /proc/<PID>/oom_score cat /proc/<PID>/oom_score_adj # Protect a critical process from the OOM killer echo -1000 > /proc/<PID>/oom_score_adj echo -500 > /proc/<PID>/oom_score_adj protect_procs=("mysqld" "redis-server" "nginx" "knot-cli") for proc in "${protect_procs[@]}"; do PID=$(pgrep -x "$proc" | head -1) if [[ -n "$PID" ]]; then echo -500 > /proc/$PID/oom_score_adj echo "Protected: $proc (PID=$PID)" fi done ``` Cache dro ...[truncated 2544 chars]
Remediation
<![CDATA[ ## Remediation Suggestions 1. Remove `barrier=0` from generic tuning recommendations and clearly discourage disabling write barriers. 2. Require verified storage guarantees, tested power-loss protection, backups, and filesystem-specific documentation before changing write-ordering behavior. 3. Generate fio paths securely and refuse to use an existing file: ```bash TEST_FILE=$(mktemp /data/fio-test.XXXXXX) || exit 1 ``` 4. Check free space, mount identity, device type, and business workload before benchmarking. 5. Use conservative fio limits, maintenance windows, I/O priorities, and explicit user confirmation. 6. Install an `EXIT`, `INT`, and `TERM` trap to remove only the exact securely created benchmark file. 7. Avoid `oom_score_adj=-1000` as a generic recommendation. Prefer bounded cgroup memory controls, service-level resource limits, and moderate adjustments. 8. Verify process executable path, owner, service unit, and PID start time before changing process attributes. 9. Use the lowest effective real-time priority, impose runtime limits, and test under controlled load. 10. Treat cache dropping as a specialized diagnostic action, not a normal optimization. Require an explicit warning and approval. 11. Record original values and provide exact rollback commands for every change. ]]>

T09 · Insecure Skill Coding Practices

Warning
Location
scripts/collect_snapshot.sh:37
Finding
Performance Snapshots May Be Written Without Confidentiality Controls<![CDATA[ ## Vulnerability Details **File Locations**: - `scripts/collect_snapshot.sh:37-114` - `scripts/collect_snapshot.sh:119-122` - `SKILL.md:354-361` **Vulnerability Type**: Sensitive operational information exposure **Risk Level**: Medium ### Vulnerable Code The snapshot collects process, network, routing, mount, and kernel information: ```bash run_cmd "CPU intensive processes TOP10" "ps aux --sort=-%cpu | head -11" run_cmd "Memory intensive processes TOP10" "ps aux --sort=-%mem | head -11" run_cmd "Mount options" "mount | grep -v 'tmpfs\|proc\|sys\|dev\|cgroup'" run_cmd "Network interface information" "ip addr show" run_cmd "Routing table" "ip route" run_cmd "Kernel log, latest 50 entries" "dmesg | tail -50" ``` The caller-supplied output is written without establishing restrictive permissions: ```bash if [[ -n "$OUTPUT" ]]; then collect | tee "$OUTPUT" echo "" echo "✅ Report saved to: $OUTPUT" else collect fi ``` The documented baseline workflow also stores snapshots in a durable shared location: ```bash bash scripts/collect_snapshot.sh > /var/log/perf-baseline-$(date +%Y%m%d).txt 0 4 1 * * bash /path/to/scripts/collect_snapshot.sh > /var/log/perf-baseline.log ``` ### Technical Analysis The data is legitimately relevant to system diagnosis, and the code does not transmit it over the network. However, the collection is broad and may include: - Hostnames and kernel versions. - Internal IP addresses and network routes. - Usernames and process command lines. - Mounted storage layout. - Kernel events and hardware details. - Service and container resource information. The script does not set `umask 077`, enforce mode `0600`, validate the destination, provide redaction, or warn the user before collecting sensitive identifiers. Output permissions therefore depend on the execution environment and caller umask. A report stored under `/tmp`, a shared support directory, or an inadequately protected `/var/log` path may become readable by u ...[truncated 997 chars]
Remediation
<![CDATA[ ## Remediation Suggestions 1. Set `umask 077` before creating any report. 2. Create output files explicitly with mode `0600`. 3. Reject symbolic-link destinations and validate ownership of existing output paths. 4. Offer collection profiles so users can select only CPU, memory, disk, or network data. 5. Add a redaction mode for IP addresses, hostnames, usernames, process arguments, and mount paths. 6. Display a clear warning describing the collected sensitive information before execution. 7. Avoid collecting full process command lines unless necessary; prefer process names or explicitly approved fields. 8. Define retention and secure deletion guidance for recurring baselines. 9. Ensure cron-generated reports are stored in a dedicated directory with restrictive ownership and permissions. 10. Warn users to review and sanitize reports before sharing them with external support systems. ]]>
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Tool MisuseTool Parameter Abuse, Chaining Abuse, Unsafe Defaults
  • Rogue AgentSelf-Modification, Session Persistence
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
Findings (35)

Tool Parameter Abuse

High
Category
Tool Misuse
Content
sysctl -w 参数名=原始值

# 持久化回滚
rm /etc/sysctl.d/99-perf-analyzer.conf
sysctl --system
```
Confidence
85% confidence
Finding
Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).

Tool Parameter Abuse

High
Category
Tool Misuse
Content
--runtime=30 --time_based --group_reporting

# 清理测试文件
rm /data/fio_test

# 性能参考(常见磁盘类型):
# ┌─────────────┬──────────────┬──────────────┬────────────┐
Confidence
85% confidence
Finding
Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).

Tool Parameter Abuse

High
Category
Tool Misuse
Content
# ... 逐一回滚

# 方案2:删除配置文件并重新加载
rm /etc/sysctl.d/99-perf-master.conf
sysctl --system
# 注意:已通过 sysctl -w 临时设置的值不会自动还原,需手动回滚
```
Confidence
85% confidence
Finding
Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).

Tool Parameter Abuse

High
Category
Tool Misuse
Content
# 删除 Swap
swapoff /swapfile
rm /swapfile
sed -i '/swapfile/d' /etc/fstab
```
Confidence
90% confidence
Finding
The document includes a destructive file deletion command, 'rm /swapfile', as part of operational guidance without strong safeguards, validation, or confirmation. In an automated agent setting, destructive commands are especially risky because they may be executed out of context, potentially removing active or needed swap configuration and causing availability degradation or boot issues when combined with fstab changes.

Natural-Language Policy Violations

Medium
Confidence
95% confidence
Finding
The skill is described entirely as a Chinese-language expert experience (“Linux 系统性能分析与调优全能专家 Skill”) with no indication that users may choose another language. Under the language/locale policy, forcing a specific language without user opt-in is a natural-language policy concern.

Vague Triggers

Medium
Confidence
95% confidence
Finding
The trigger phrases are broad, natural-language requests such as general complaints about slowness or asking for help tuning kernel parameters. This can cause the skill to activate in contexts the user did not explicitly intend, increasing the chance that it provides invasive diagnostics or risky system-tuning guidance unexpectedly. In a performance-tuning skill, unintended activation is more dangerous because the skill’s domain includes privileged commands, kernel/sysctl changes, and production-impacting recommendations.

Missing User Warnings

Medium
Confidence
91% confidence
Finding
This section presents multiple privileged, system-modifying tuning commands (for memory, CPU, I/O, and network behavior) before clearly and locally warning about prerequisites, persistence, rollback, and service impact. In an agent skill context, users may copy or execute these commands directly, causing instability, degraded performance, or outages if applied to the wrong workload or environment.

Missing User Warnings

Medium
Confidence
95% confidence
Finding
The persistence section writes kernel settings into /etc/sysctl.d and later removes that file with rm, but the same section does not prominently warn that these changes affect system-wide behavior across reboots and may break applications or networking. In a skill intended to guide operational actions, this increases the chance of unsafe system-wide configuration drift or accidental rollback of unrelated settings if users adapt the example carelessly.

Missing User Warnings

Medium
Confidence
96% confidence
Finding
This section gives root-level memory and kernel tuning commands that persistently modify sysctl settings, transparent huge page behavior, and OOM protection without safety framing. In a performance-tuning skill, users are likely to copy commands directly, and bad fit for workload or environment can cause instability, unexpected memory behavior, or make the system harder to recover under memory pressure.

Missing User Warnings

Medium
Confidence
97% confidence
Finding
This section recommends persistent network-stack and file-descriptor tuning by writing directly into /etc/sysctl.d and /etc/security/limits.conf, but does not warn about connectivity regressions, application incompatibility, or the fact that some TCP settings are deprecated or context-dependent. Because these changes affect the whole host and are presented as a straightforward fix for high concurrency, an operator could degrade networking or impact unrelated services.

Missing User Warnings

Medium
Confidence
95% confidence
Finding
The document advises changing the block scheduler and VM dirty-page writeback parameters at a low level without warning that the effects are workload-, device-, and kernel-specific. Incorrect tuning here can increase latency, worsen throughput, or create broader system instability, especially since the example also involves a disk already showing hardware faults.

Missing User Warnings

Medium
Confidence
99% confidence
Finding
The heap-dump instruction writes a full JVM memory snapshot to /tmp without warning that heap dumps often contain credentials, tokens, PII, and business data. /tmp is commonly less controlled, may be world-accessible depending on environment, and can expose sensitive contents to other local users or collection pipelines.

Natural-Language Policy Violations

Medium
Confidence
92% confidence
Finding
This markdown file presents the skill/reference content exclusively in Chinese, starting from the title, and nowhere indicates that the language is optional or limited to a specific region-specific audience. Under the policy, forcing a specific language without user opt-in is a natural-language policy violation.

Session Persistence

Medium
Category
Rogue Agent
Content
[Install]
WantedBy=multi-user.target
EOF
systemctl enable --now cpu-performance.service

# 查看 CPU 当前频率
cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_cur_freq | awk '{s+=$1; n++} END {printf "平均: %.0f MHz\n", s/n/1000}'
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.

Session Persistence

Medium
Category
Rogue Agent
Content
[Install]
WantedBy=multi-user.target
EOF
systemctl enable --now cpu-performance.service

# 查看 CPU 当前频率
cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_cur_freq | awk '{s+=$1; n++} END {printf "平均: %.0f MHz\n", s/n/1000}'
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.

Session Persistence

Medium
Category
Rogue Agent
Content
[Install]
WantedBy=multi-user.target
EOF
systemctl enable --now cpu-performance.service

# 查看 CPU 当前频率
cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_cur_freq | awk '{s+=$1; n++} END {printf "平均: %.0f MHz\n", s/n/1000}'
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.

Missing User Warnings

Medium
Confidence
93% confidence
Finding
The document contains numerous privileged, system-modifying commands that alter I/O schedulers, queue depths, mount options, sysctl settings, udev rules, systemd timers, and cron entries, but it does not begin with a clear safety notice about required privileges, persistence, rollback needs, workload-specific applicability, or risks such as data loss and degraded stability. In a performance-tuning skill, users are likely to copy commands directly, so the absence of upfront warnings materially increases the chance of harmful misconfiguration.

Session Persistence

Medium
Category
Rogue Agent
Content
systemctl enable --now smartd
# 配置 /etc/smartd.conf 发现问题时发邮件

# 添加定期检查到 crontab
echo "0 3 * * 0 smartctl -a /dev/sda > /var/log/smart-sda-$(date +\%Y\%W).log" >> /etc/crontab
```
Confidence
85% 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.

Missing User Warnings

Medium
Confidence
91% confidence
Finding
This section provides privileged, system-wide configuration commands that persistently alter kernel and networking behavior, but it does not prominently warn that root access is required, that changes can disrupt connectivity or stability, or that settings are workload-specific. In a performance-tuning skill, users may copy-paste the block directly into production, creating avoidable outage risk.

Missing User Warnings

Medium
Confidence
95% confidence
Finding
This section provides direct system-modifying commands for swap creation, swappiness tuning, and swap deletion without a prominent safety warning, prerequisites, rollback guidance, or validation steps before destructive actions. An agent or user following this guidance blindly could alter memory behavior, corrupt availability expectations, or break boot/runtime configuration through unsafe edits to /etc/fstab and swap state.

Sudo/Root Execution

Medium
Category
Privilege Escalation
Content
# 创建 Swap 文件(系统无 Swap 时)
fallocate -l 4G /swapfile
chmod 600 /swapfile
mkswap /swapfile
swapon /swapfile
echo '/swapfile none swap sw 0 0' >> /etc/fstab
Confidence
80% confidence
Finding
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.

Missing User Warnings

Medium
Confidence
95% confidence
Finding
The THP, HugePage, dirty page, cache drop, and memory reclamation guidance includes kernel and memory-management changes that can materially affect latency, throughput, and stability, yet the warnings are inconsistent and not prominent. Commands such as disabling THP, changing dirty ratios, enabling persistent services, or dropping caches can cause immediate service impact if applied in production without qualification.

Session Persistence

Medium
Category
Rogue Agent
Content
[Install]
WantedBy=multi-user.target
EOF
systemctl enable --now disable-thp.service

# 验证
cat /sys/kernel/mm/transparent_hugepage/enabled   # 应显示 never
Confidence
84% confidence
Finding
Persistently enabling a new systemd service changes system behavior across reboots and extends the blast radius of a tuning action beyond the current troubleshooting session. In an agent skill context, instructing automatic persistence without explicit user approval can create hard-to-detect configuration drift and prolonged service-impacting behavior.

Missing User Warnings

Medium
Confidence
93% confidence
Finding
This section appends persistent sysctl changes to `/etc/sysctl.d/99-perf-master.conf`, modifying host-wide TCP behavior without clearly warning that the changes affect the entire system and may degrade connectivity, stability, or compatibility for unrelated workloads. In a troubleshooting skill, such commands are contextually relevant, but presenting them as copy-paste guidance without explicit cautions, prerequisites, rollback steps, or environment scoping creates unsafe operational advice.

Missing User Warnings

Medium
Confidence
97% confidence
Finding
The complete example writes a broad set of kernel networking parameters and immediately applies them with `sysctl -p`, causing instant host-wide changes that can disrupt production traffic, weaken reliability assumptions, or create hard-to-diagnose regressions if used blindly. The skill’s performance-tuning context makes such content expected, but bundling many aggressive settings into a ready-to-run block materially increases danger because users may execute it without understanding workload, kernel-version, or environment-specific constraints.

Static analysis

No suspicious patterns detected.