other
- Location
scripts/docs-generator.sh:94- Finding
Undisclosed Promotional Content Injected into Generated Documentation
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill mostly matches its documentation-generator purpose, but it also ships an undisclosed local utility that can persistently store and log user-provided text.
Review this before installing. The documented generator is local and does not appear to exfiltrate data, but avoid invoking the bundled script.sh with secrets or confidential text because it can retain arguments on disk. Also review generated documents before committing or publishing them because they include hardcoded BytesAgain attribution.
scripts/docs-generator.sh:94Undisclosed Promotional Content Injected into Generated Documentation
scripts/script.sh:5Undocumented Persistent Storage of Raw Command Arguments
The declared purpose is documentation generation, but the detected behavior reportedly performs persistent local storage, logging/history collection, and generic database-like add/list/search/export operations while lacking actual documentation-generation functionality. That is a strong deception signal: a user may authorize or run the skill expecting harmless doc creation while it instead accumulates data locally and enables collection/export of potentially sensitive content.
The script's functionality materially contradicts the declared purpose of the skill: instead of generating documentation, it acts as a generic local logger/list manager with persistent storage. This kind of capability mismatch is dangerous because users or calling systems may grant trust, permissions, or workflow placement based on the advertised documentation role, while the script silently stores user-provided data and command history on disk.
The skill advertises executable usage via a shell script and static analysis detected network-capable code, yet the manifest declares no permissions or allowed-tools scope. That lack of explicit tool scoping reduces transparency and weakens enforcement boundaries, making it easier for the skill to perform unexpected outbound actions if executed in an agent environment.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
]
print("## {} API".format(resource.capitalize()))
print("")
print("Base URL: `https://api.example.com/v1`")
print("")
print("### Endpoints")
print("")
The inline help and comments describe the tool as a 'multi-purpose utility tool,' directly conflicting with the skill metadata that presents it as a documentation generator. This inconsistency increases security risk because it obscures the true behavior of the asset, making review, approval, and least-privilege decisions less reliable.
The script persistently writes entries to data.log and records command activity in history.log under a user-controlled data directory without clearly warning the user that inputs and actions are being retained. In a skill context, this is risky because user-supplied content may include sensitive project names, tokens, internal paths, or other confidential data that becomes locally stored unexpectedly.
No suspicious patterns detected.