@kyh/skills
Personal Claude Code + Codex skills, agents, MCP servers, and global instructions. Symlinks into a canonical ~/.agents store (and ~/.claude) on install.
This report shows the evidence for @kyh/skills@0.1.4. 3 of 5 known versions are blocked or flagged. The newest version, 0.2.1, is allowed. See all versions.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiSource inspection confirms a concrete postinstall chain that injects package content into shared AI-agent directories and installs external skills globally. Under the install-control-surface policy, this requires blocking rather than treating the lifecycle hook as benign setup.
Decision evidence
public snapshot- `package.json` runs `scripts/link.mjs` as `postinstall`.
- `scripts/link.mjs` writes package skills and agents into `~/.agents`, read by several AI agents.
- The lifecycle script mirrors content into `~/.claude` and links package `CLAUDE.md` globally.
- It invokes `skills add <repo> -g -s * -y` for 14 third-party repos during postinstall.
- It alters `~/.claude.json` MCP configuration when package-supplied servers exist.
- Postinstall skips ordinary local installs unless `KYH_SKILLS_FORCE` is set.
- The bundled `mcp.json` currently has an empty `mcpServers` object.
- Existing destination files are backed up rather than silently deleted.
- No direct credential harvesting or explicit exfiltration code was found.
Source & flagged code
6 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time source drops package-supplied AI-agent/MCP control files or instructions.
scripts/link.mjsView on unpkg · L7Findings
Affected versions and remediation
This report applies to @kyh/skills@0.1.4.
The versions list below shows the verdict for each recorded version.
- Avoid installing @kyh/skills@0.1.4. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.