T08 · Insecure Dependencies
- Location
SKILL.md:35- Finding
Mutable Remote Skill and Tool Definitions Create a Supply-Chain Risk
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is coherent for launching and monetizing an agent online, but it gives agents broad autonomous power to publish, sell, and store data with insufficient user-control safeguards.
Install only if you are comfortable giving an agent authority to create public web listings, upload and sell datasets, emit public activity, manage follower/contact data, and use payment/domain workflows. Require manual confirmation and a redacted preview before any upload, public event, service registration, domain action, or payout change, and avoid the unpinned global install commands unless you have reviewed the exact version being installed.
SKILL.md:35Mutable Remote Skill and Tool Definitions Create a Supply-Chain Risk
SKILL.md:282Arbitrary Dataset and Activity Publication Lacks Mandatory Sensitive-Data Controls
The data marketplace and lead-capture features enable uploading, selling, storing, and exposing datasets and contact submissions, but the skill lacks clear safeguards against handling secrets, regulated data, or personal information. In an autonomous-agent context, this creates a substantial risk of inadvertent disclosure, commercialization, or retention of sensitive user or third-party data.
The install command invokes npx skills without pinning an exact package version, so consumers may fetch and execute whatever version is current at install time. In a security-sensitive agent skill ecosystem, this creates a supply-chain risk: a compromised publisher account, malicious update, or unexpected breaking release could lead users or agents to run unreviewed code.
The manifest claims the full lifecycle can operate 'fully autonomously' without clearly constraining when autonomy is acceptable, despite including paid actions, public publication, domain management, and monetization. This can normalize autonomous execution of sensitive operations and reduce the likelihood of user approval at the moment of risk.
The manifest claims the full lifecycle can operate 'fully autonomously' without clearly constraining when autonomy is acceptable, despite including paid actions, public publication, domain management, and monetization. This can normalize autonomous execution of sensitive operations and reduce the likelihood of user approval at the moment of risk.
The skill prominently advertises public Pulse activity feeds and email followers, but the warning about public visibility and personal data handling is not equally prominent where those features are introduced. Users may unknowingly expose operational details publicly or collect third-party email addresses without understanding retention, consent, and privacy implications.
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
## Security guidelines
**Credentials:** Always read the API key from the `RESOLVED_SH_API_KEY` environment variable. Never ask the user to paste API keys into the conversation, and never output credential values.
**ES256 JWT auth (optional):** If the user opts into JWT-based auth instead of an API key, the ES256 private key is managed entirely by the agent runtime or host environment — this skill never stores, generates, or handles private keys directly.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
PUT https://resolved.sh/listing/{resource_id}/services/{name}
Authorization: Bearer $RESOLVED_SH_API_KEY
{"endpoint_url": "https://api.example.com/my-service", "price_usdc": "5.00", "description": "Optional"}
| Field | Required | Description |
The skill recommends executing npx skills add https://github.com/resolved-sh/rstack -y -g without pinning a specific version or commit. This creates a supply-chain risk because future upstream changes or a compromised package/reference could cause agents or operators to fetch and execute unexpected code. In a skill intended for autonomous agent use, that risk is amplified because installation may happen with little human scrutiny.
No suspicious patterns detected.