modly-cli
Use when an agent needs to call a running Modly desktop instance from the terminal to generate/export image-to-3D assets through canonical JSON-first automation commands.
67
83%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
Low
Low-risk findings.
1 low severity finding. Worth noting, but not necessarily harmful.
W011: Third-party content exposure detected (indirect prompt injection risk).
What this means
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
Why it was flagged
The required runtime workflow for canonical commands (`health`, `model`, `workflow-run`, `capability`, `process-run`, `generate`) makes HTTP requests to the local Modly FastAPI server and ingests its JSON responses (potential outsider-authored content) into the CLI’s emitted stdout/stderr context, i.e., `_request_json` reads response text and `cmd_*` prints it via `_json_print`.
- Repository
- lightningpixel/modly
- Commit
3ae371c
- Audited
- Security analysis
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.