Security audit
Security checks for vulnerabilities and agentic risk
The scanners classify this skill as benign, with medium confidence, while flagging unpinned package commands and a possible privacy issue around playground links; coverage is partial.
The verdict is benign, not risk-free. Before installing, consider whether you are comfortable with unpinned package commands and with a workflow that may create a playground link containing floor-plan information. Coverage is incomplete: the scanner reported unresolved local references, so its results do not establish that every referenced item was reviewed.
The compatibility instructions recommend executing an npm package without specifying a version, allowing the code obtained during setup to change without review. Although this is a CLI rather than an MCP server, a compromised package release or dependency could execute with the agent's filesystem and credential access.
The setup command uses unversioned npx execution, and -y suppresses the installation confirmation. This is a conventional setup pattern rather than evidence of malicious intent, but it can automatically execute a newly compromised release with the agent's privileges.
The instruction to substitute unversioned npx calls for every CLI invocation propagates the same supply-chain exposure throughout the workflow. It makes the executable version environment-dependent rather than tying execution to reviewed code; it does not prove that every invocation downloads a fresh release.
The standard delivery workflow directs the agent to generate a third-party playground link without first addressing whether the user permits sharing their building layout. The supplied text does not establish whether link generation uploads data or encodes it locally, but a plan-bearing URL can disclose sensitive layout information when shared or opened, depending on the URL format and service behavior.
The delivery step again recommends executing an unpinned npm package, this time while processing the user's completed floor plan. A compromised release could access that plan and other files available to the agent; this repeats the setup vulnerability rather than establishing a separate malicious mechanism.
The optional npx skills command executes an unversioned installer and references a repository without an immutable revision. Although neither is an MCP server, a compromised installer could execute code, and changed repository content could introduce unreviewed instructions into the agent's future workflow.
