Security audit
Security checks for vulnerabilities and agentic risk
This skill is a marketplace/payment assistant, but it also claims broad command, file, and API capabilities without clear limits or payment safeguards.
Review this skill carefully before installing. Do not let it post jobs, bid, spend USDC, access wallet credentials, write files, call external services, or run shell commands unless you explicitly approve the exact action, amount, destination, and command/API scope.
The activation guidance is overly broad, encouraging use across loosely defined AI-model, orchestration, and LLM scenarios without narrowing preconditions or risk boundaries. Broad invocation criteria make accidental triggering more likely in contexts where external calls, payment-related actions, or command execution would be inappropriate.
The skill presents conflicting descriptions of its purpose: it is framed as a job-marketplace CLI, but the same section advertises generic file handling, API integration, information retrieval, and command execution. This ambiguity materially increases the chance that an agent or user will authorize broader behaviors than intended, including shell execution or external access under an unrelated trust assumption.
The skill advertises file processing, API integration, and command execution but does not place a prominent warning alongside those capabilities about writes, external network activity, or shell risks. In a skill that also mentions payments and automation, missing upfront warnings can lead users or agents to approve dangerous operations without informed consent.
The file contradicts itself on whether it is a pure Markdown/natural-language skill or an execute()/command-capable skill. That inconsistency can cause an agent runtime or operator to treat it as low-risk documentation while it implicitly authorizes higher-risk actions such as command execution.
No suspicious patterns detected.
