T01 · Skill Instruction Hijacking
- Location
SKILL.md:50- Finding
Non-Optional Agent Workflow Directives Override User Control
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This appears to be a real skill-audit/refactor tool, but it asks the agent to keep modifying files without user confirmation and includes under-disclosed cleanup and reporting risks.
Review before installing. Use read-only audit modes first, keep a separate backup of any target skill, and do not allow update/refactor/cleanup to run automatically without reviewing the planned file changes and deletion targets.
SKILL.md:50Non-Optional Agent Workflow Directives Override User Control
scripts/permission_checker.py:43Detection Signatures Are Deliberately Obfuscated to Evade Static Scanners
scripts/cleanup_manager.py:46Cleanup Root and Deletion Containment Can Be Manipulated
Backup rollback, restore, purge, and diff inspection are operationally powerful file-management functions that are not implied by the stated standards-audit purpose. Undisclosed disaster-recovery and restoration actions can materially alter user files and should not be hidden behind a compliance-engine label.
Backup rollback, restore, purge, and diff inspection are operationally powerful file-management functions that are not implied by the stated standards-audit purpose. Undisclosed disaster-recovery and restoration actions can materially alter user files and should not be hidden behind a compliance-engine label.
Backup rollback, restore, purge, and diff inspection are operationally powerful file-management functions that are not implied by the stated standards-audit purpose. Undisclosed disaster-recovery and restoration actions can materially alter user files and should not be hidden behind a compliance-engine label.
Backup rollback, restore, purge, and diff inspection are operationally powerful file-management functions that are not implied by the stated standards-audit purpose. Undisclosed disaster-recovery and restoration actions can materially alter user files and should not be hidden behind a compliance-engine label.
Backup rollback, restore, purge, and diff inspection are operationally powerful file-management functions that are not implied by the stated standards-audit purpose. Undisclosed disaster-recovery and restoration actions can materially alter user files and should not be hidden behind a compliance-engine label.
Backup rollback, restore, purge, and diff inspection are operationally powerful file-management functions that are not implied by the stated standards-audit purpose. Undisclosed disaster-recovery and restoration actions can materially alter user files and should not be hidden behind a compliance-engine label.
Backup rollback, restore, purge, and diff inspection are operationally powerful file-management functions that are not implied by the stated standards-audit purpose. Undisclosed disaster-recovery and restoration actions can materially alter user files and should not be hidden behind a compliance-engine label.
Backup rollback, restore, purge, and diff inspection are operationally powerful file-management functions that are not implied by the stated standards-audit purpose. Undisclosed disaster-recovery and restoration actions can materially alter user files and should not be hidden behind a compliance-engine label.
Backup rollback, restore, purge, and diff inspection are operationally powerful file-management functions that are not implied by the stated standards-audit purpose. Undisclosed disaster-recovery and restoration actions can materially alter user files and should not be hidden behind a compliance-engine label.
Backup rollback, restore, purge, and diff inspection are operationally powerful file-management functions that are not implied by the stated standards-audit purpose. Undisclosed disaster-recovery and restoration actions can materially alter user files and should not be hidden behind a compliance-engine label.
Backup rollback, restore, purge, and diff inspection are operationally powerful file-management functions that are not implied by the stated standards-audit purpose. Undisclosed disaster-recovery and restoration actions can materially alter user files and should not be hidden behind a compliance-engine label.
Backup rollback, restore, purge, and diff inspection are operationally powerful file-management functions that are not implied by the stated standards-audit purpose. Undisclosed disaster-recovery and restoration actions can materially alter user files and should not be hidden behind a compliance-engine label.
Backup rollback, restore, purge, and diff inspection are operationally powerful file-management functions that are not implied by the stated standards-audit purpose. Undisclosed disaster-recovery and restoration actions can materially alter user files and should not be hidden behind a compliance-engine label.
Backup rollback, restore, purge, and diff inspection are operationally powerful file-management functions that are not implied by the stated standards-audit purpose. Undisclosed disaster-recovery and restoration actions can materially alter user files and should not be hidden behind a compliance-engine label.
Backup rollback, restore, purge, and diff inspection are operationally powerful file-management functions that are not implied by the stated standards-audit purpose. Undisclosed disaster-recovery and restoration actions can materially alter user files and should not be hidden behind a compliance-engine label.
Backup rollback, restore, purge, and diff inspection are operationally powerful file-management functions that are not implied by the stated standards-audit purpose. Undisclosed disaster-recovery and restoration actions can materially alter user files and should not be hidden behind a compliance-engine label.
Backup rollback, restore, purge, and diff inspection are operationally powerful file-management functions that are not implied by the stated standards-audit purpose. Undisclosed disaster-recovery and restoration actions can materially alter user files and should not be hidden behind a compliance-engine label.
Backup rollback, restore, purge, and diff inspection are operationally powerful file-management functions that are not implied by the stated standards-audit purpose. Undisclosed disaster-recovery and restoration actions can materially alter user files and should not be hidden behind a compliance-engine label.
Backup rollback, restore, purge, and diff inspection are operationally powerful file-management functions that are not implied by the stated standards-audit purpose. Undisclosed disaster-recovery and restoration actions can materially alter user files and should not be hidden behind a compliance-engine label.
Referenced artifact was not completely inspected
- **版本号三端一致** — 更新时同步 `SKILL.md` / `_meta.json` / `references/changelog.md`
Referenced artifact was not completely inspected
- **版本号三端一致** — 更新时同步 `SKILL.md` / `_meta.json` / `references/changelog.md`
Lines L184-L186 explicitly claim that all review results are 'pure warning mode' and that scripts.skill_audit always returns exit code 0 even for ERROR findings. Later, L354-L360 discusses audit --verify returning exit(1), which is an active contradiction in the skill's own documentation about enforcement behavior.
The CLI claims to support --dry-run, but still calls finalize() and run_cleanup() before printing dry-run output. A user relying on dry-run for safe preview will instead trigger real deletion, creating a high risk of unintended destructive file removal in an operational tool.
The implementation marks results as PASS (LLM 二筛通过) and removes all failing entries merely because a classify file exists, instead of filtering only explicitly classified false positives. This can hide genuine failures and produce falsely clean audit reports, enabling policy bypass and unsafe changes to be approved under the appearance of compliance.
fix_artifact_paths performs real destructive and restructuring actions on the target skill: it deletes files matching broad patterns, moves files based on analyzer output, and rewrites references across the tree. For a standards-audit/fix tool, this exceeds low-risk metadata repair and can cause data loss or unintended repository-wide changes if findings are wrong, incomplete, or attacker-influenced.
Detected: suspicious.dynamic_code_execution