Audit History

Version	Date	Result	Change vs previous
v8 Latest	9 июл. 2026 г., 01:46	1 confirmed	No capability change
v7	9 июл. 2026 г., 01:46	1 confirmed	No capability change
v6	5 июл. 2026 г., 13:41	No confirmed findings	No capability change
v5	5 июл. 2026 г., 13:41	No confirmed findings	No capability change
v4	27 июн. 2026 г., 18:47	1 confirmed	No capability change
v3	16 янв. 2026 г., 14:06	No confirmed findings	No capability change
v2	16 янв. 2026 г., 14:06	No confirmed findings	External commandsFilesystem access
v1	10 янв. 2026 г., 09:32	No confirmed findings	Baseline

9 июл. 2026 г., 01:46

Most static findings are false positives caused by Markdown code fences, inline shell syntax, and benign shell examples. One finding is confirmed: the text processing example reads /etc/passwd, which is a sensitive host file and should not appear as a general-purpose scripting example.

1

Files scanned

357

Lines analyzed

3

Review items

0

False positives ignored

Confirmed security concerns (1)

Critical

SKILL.md:318

System password file access

awk -F: '{print $1}' /etc/passwd # Custom delimiter

The example directly reads /etc/passwd, a sensitive system account file. Even as documentation, this normalizes access to sensitive host data in generated shell commands.

Detected Patterns

System password file access

Audited by: claude

Audit version 7

9 июл. 2026 г., 01:46

Most static findings are false positives caused by Markdown code fences, inline shell syntax, and benign shell examples. One finding is confirmed: the text processing example reads /etc/passwd, which is a sensitive host file and should not appear as a general-purpose scripting example.

1

Files scanned

357

Lines analyzed

3

Review items

0

False positives ignored

Confirmed security concerns (1)

Critical

SKILL.md:318

System password file access

awk -F: '{print $1}' /etc/passwd # Custom delimiter

The example directly reads /etc/passwd, a sensitive system account file. Even as documentation, this normalizes access to sensitive host data in generated shell commands.

Detected Patterns

System password file access

Audited by: claude

Audit version 6

5 июл. 2026 г., 13:41

The static findings are false positives caused by Markdown shell examples, inline best-practice text, and placeholder file names. No prompt injection, malicious intent, data exfiltration, or executable skill code was found in SKILL.md.

1

Files scanned

357

Lines analyzed

2

Review items

1

False positives ignored

Static false positives ignored (1)

These static matches were dismissed by semantic review or matched schema-only tokens, so they are shown for transparency but do not drive the quality score.

Critical

SKILL.md:318

System password file access

awk -F: '{print $1}' /etc/passwd # Custom delimiter

Force-confirmed blocker/critical static finding; AI dismissal overridden.

Audited by: codex

Audit version 5

5 июл. 2026 г., 13:41

The static findings are false positives caused by Markdown shell examples, inline best-practice text, and placeholder file names. No prompt injection, malicious intent, data exfiltration, or executable skill code was found in SKILL.md.

1

Files scanned

357

Lines analyzed

2

Review items

1

False positives ignored

Static false positives ignored (1)

These static matches were dismissed by semantic review or matched schema-only tokens, so they are shown for transparency but do not drive the quality score.

Critical

SKILL.md:318

System password file access

awk -F: '{print $1}' /etc/passwd # Custom delimiter

Force-confirmed blocker/critical static finding; AI dismissal overridden.

Audited by: codex

Audit version 4

27 июн. 2026 г., 18:47

Static analysis found many shell command, substitution, filesystem, weak crypto, and password-file patterns, but these occur inside Markdown examples for a shell scripting guide. No prompt injection, network access, credential exfiltration, or executable payload was found. The only retained concern is that one example reads /etc/passwd, which is educational but should be treated as sensitive system-file access.

1

Files scanned

357

Lines analyzed

3

Review items

3

False positives ignored

Confirmed security concerns (1)

Low

SKILL.md:318

System Account File Used In Example

The guide includes an awk example that reads /etc/passwd. This appears to be a common delimiter example, not malicious code, but it normalizes reading a sensitive system account file.

The exact path /etc/passwd is present in the documented command, so the sensitive-file pattern is real. Confidence is not higher because the context is an educational text-processing example rather than an executable payload.

Static false positives ignored (3)

These static matches were dismissed by semantic review or matched schema-only tokens, so they are shown for transparency but do not drive the quality score.

Low

SKILL.md:31-96 SKILL.md:102-107 SKILL.md:303-325 SKILL.md:331-343

Benign Shell Examples Trigger Command Execution Patterns

The static analyzer detected many command execution and command substitution patterns. They are contained in Markdown code fences and best-practice notes for a shell scripting guide, with no evidence of automatic execution.

The suspicious commands appear inside fenced Markdown examples and explanatory bullet lists. I found no executable script file, install hook, network call, or hidden command runner.

Low

SKILL.md:3-4 SKILL.md:34 SKILL.md:338

Weak Crypto Static Matches Are False Positives

Static weak-cryptography matches point to shell-related text such as the Bash and Zsh description, a script description comment, and exit-code guidance. No hashing or encryption implementation is present.

The cited lines do not contain cryptographic APIs or algorithm choices. They are natural-language shell documentation, so the weak crypto classification is unsupported.

Low

SKILL.md:313

Certificate Or Key Static Match Is False Positive

The certificate or key-file match points to a jq example selecting a JSON field named key. It does not reference private keys, certificates, or credential files.

The cited line uses the literal JSON property name key in a jq tutorial example. There is no evidence of file access to certificate material or secrets.

Risk Factors

⚙️ External commands (6)

SKILL.md:31-96 SKILL.md:102-107 SKILL.md:111-120 SKILL.md:124-141 SKILL.md:303-325 SKILL.md:331-343

📁 Filesystem access (3)

SKILL.md:126 SKILL.md:293 SKILL.md:318

Detected Patterns

Shell Command Documentation ExamplesSystem File Path Example

Audited by: codex

Audit version 3

16 янв. 2026 г., 14:06

Pure documentation skill containing markdown guidance only. The static scanner flagged 62 potential issues, but ALL are false positives because this skill contains no executable code - only instructional shell scripting patterns in markdown code blocks.

2

Files scanned

535

Lines analyzed

2

Review items

0

False positives ignored

Audited by: claude

Audit version 2

16 янв. 2026 г., 14:06

Pure documentation skill containing markdown guidance only. The static scanner flagged 62 potential issues, but ALL are false positives because this skill contains no executable code - only instructional shell scripting patterns in markdown code blocks.

2

Files scanned

535

Lines analyzed

2

Review items

0

False positives ignored

Audited by: claude

Audit version 1

10 янв. 2026 г., 09:32

Pure documentation skill containing markdown guidance only. No executable code, network access, file system modifications, or external command execution capabilities. All content is instructional shell scripting best practices.

1

Files scanned

357

Lines analyzed

0

Review items

0

False positives ignored

No confirmed security findings were recorded for this completed audit.

Audited by: claude

Version comparison

Confirmed security concerns (1)

Risk Factors

Detected Patterns

Confirmed security concerns (1)

Risk Factors

Detected Patterns

Risk Factors

Risk Factors

Confirmed security concerns (1)

Risk Factors

Detected Patterns

Risk Factors

Risk Factors