T08 · Insecure Dependencies
- Location
scripts/package.json:9- Finding
Mutable npm Dependency Installed Without a Lockfile
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill does what it advertises, but users should understand it can spend API credits, send manuscript content to Anthropic, and create many local files.
Install only if you are comfortable sending book ideas and generated manuscript material to Anthropic and paying for the resulting API calls. Use an explicit output directory, avoid sensitive unpublished or personal material unless acceptable under your Anthropic account terms, and prefer pinning dependencies with a lockfile before running npm install.
scripts/package.json:9Mutable npm Dependency Installed Without a Lockfile
scripts/generate.js:26Unvalidated Workload Arguments Permit Denial of Service and Excessive API Spending
Referenced artifact was not completely inspected
Task: Full planning prompt (see scripts/generate.js `buildPlannerPrompt`)
The invocation phrase "Write me a book about [your idea]" is extremely broad and closely resembles normal user conversation, making accidental or unintended triggering likely in an agent environment. Because this skill launches a high-cost, autonomous multi-stage content generation workflow, a casual phrase could cause unexpected API usage, long-running tasks, or publication-oriented actions without explicit user intent.
The environment section asks the user to export ANTHROPIC_API_KEY but does not explicitly warn that the skill will use that credential to make external API calls throughout the multi-agent pipeline. In context, the workflow generates many stages and parallel chapter jobs, so users may incur unexpected outbound data sharing and usage charges if they do not realize their key will be used automatically.
The trigger phrases are extremely broad (e.g. 'Write me a book about [idea]' / 'Generate a bestseller about [idea]') and are likely to match ordinary conversational requests, causing the agent to enter an autonomous workflow without explicit confirmation. In this skill, that workflow leads to file creation, parallel subagent spawning, and downstream API-backed content generation, so accidental activation can produce unintended actions and costs.
The skill instructs the agent to create an output directory and write multiple files under ~/Desktop/books/[slug]/ without an upfront user warning or approval gate. Because this is in agent-orchestrated mode triggered by ordinary writing requests, it can modify the local filesystem unexpectedly and at scale as part of a multi-step autonomous pipeline.
The script sends user-supplied ideas, generated plans, character profiles, chapter text, and editorial content to Anthropic via client.messages.create without any explicit notice, consent flow, or data minimization. In a long-form book-generation workflow, this can expose sensitive unpublished manuscripts, proprietary business ideas, memoir details, or personal data to a third-party API, creating confidentiality and compliance risks.
The script imports execSync from child_process, which would enable shell command execution, but the advertised purpose is generating and packaging book content via an LLM pipeline. Shell execution is not justified by the stated manuscript-generation scope, and no code in this file uses it.
The dependency uses a caret range (^0.39.0) instead of an exact pinned version, which permits installation of different releases over time. That weakens build reproducibility and can inadvertently pull in a vulnerable or breaking SDK version, which is more concerning here because this skill is an autonomous content-generation pipeline likely to handle API keys and file operations.
"generate": "node generate.js"
},
"dependencies": {
"@anthropic-ai/sdk": "^0.39.0"
},
"engines": {
"node": ">=18.0.0"
The manifest references @anthropic-ai/sdk without an exact pin, and the package has known advisories affecting some releases, so the actual installed version may be vulnerable without visibility from the manifest alone. In this skill context, the SDK is central to an autonomous multi-agent workflow and may interact with local files or tooling, which increases the practical risk of any SDK sandbox-escape or insecure-permission issue.
No suspicious patterns detected.