Ae1
- Category
- analysis-evasion
- Confidence
- 100% confidence
- Finding
Referenced artifact was not completely inspected
- Content
md - `SKILL.md` - This documentation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is a coherent VAM scripting reference with example scripts; its local state and file operations are disclosed and fit the stated purpose.
Install only if you want VAM Scripter documentation and example scripts. Before copying examples into VAM, review any use of fs.writeSceneFileSync or fs.unlinkSceneFileSync because those can save, overwrite, or delete scene-local files, and verify atom names, audio clips, and keybindings match your scene.
Referenced artifact was not completely inspected
- `SKILL.md` - This documentation
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.
}
});
// Save state to file
function saveState() {
try {
fs.writeSceneFileSync(statePath, JSON.stringify(appState, null, 2));
This markdown file documents a state-persistence.js example that saves and loads state across sessions and also lists an fs module for file system operations. The README does not include any warning that these behaviors may write data or persist changes, which is relevant user-facing disclosure for a markdown skill description.
This markdown file documents file-system persistence using fs.writeSceneFileSync and fs.readSceneFileSync, which can affect user data by storing and overwriting scene-specific files. The example presents the behavior as a normal pattern but does not warn users that script state will be written to disk or describe persistence implications.
The introductory sentence includes Chinese text (实用) inside an otherwise English document, which imposes mixed-language content without user opt-in or explanation. This can violate language/locale policy where skills are expected to present language consistently unless a choice or justification is provided.
The state persistence example writes state.json on disable via fs.writeSceneFileSync, which affects user data on disk. In this markdown description, there is no warning or note that the pattern persists data locally, so readers are not alerted to the side effect.
This markdown file documents fs.unlinkSceneFileSync(path) with the brief description 'Deletes a file' and an example invocation, but it does not include any cautionary note about data loss or irreversible deletion. Under the markdown-specific SQP-2 criteria, destructive behavior that can affect user data should be accompanied by a warning.
The inline comment says the sound is played 'if collision detected', but the actual condition at L18 is a distance threshold check, not a collision test. This is an intent-level documentation mismatch because it describes a different interaction model than the implemented behavior.
No suspicious patterns detected.