agentic-awesome-skills@16.6.0
AAS Core: complete local skill discovery, agent-owned selection, stack validation, and planning, backed by 2,108+ agentic skills.
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThis is a user-invoked agent-extension installer with broad capability impact, so it warrants a warning. Source inspection found no automatic lifecycle hook or concrete malicious payload chain.
Decision evidence
public snapshot- The executable installer targets several AI-agent skill directories, including Codex and Antigravity.
- On explicit execution, the installer clones a remote repository and installs its selected contents into those agent directories.
- The package ships a large skill catalog containing user-run scripts that send supplied tokens and input to external service APIs.
- package.json contains no preinstall, install, or postinstall lifecycle hook.
- The installer is a bin command, so its mutation requires a user invoking it.
- The Apify and Hugging Face examples use named environment tokens for their corresponding service endpoints; no source shows unrelated credential harvesting.
- The Fedora installer finding is an isolated test runner that sets HOME to a temporary directory.
- The PDF is a ReportLab-generated document, not an inspectable executable payload.
Source & flagged code
12 flagged · loading sourcePackage contains a high-severity secret pattern.
skills/developer-signup-flow/SKILL.mdView on unpkg · L165Stripe test secret key in skills/developer-signup-flow/SKILL.md
skills/developer-signup-flow/SKILL.mdView on unpkg · L165Findings
Affected versions and remediation
This report applies to agentic-awesome-skills@16.6.0.
See all versions of agentic-awesome-skills for other recorded verdicts.
- Review the evidence and your use of agentic-awesome-skills@16.6.0 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.