Security audit
Security checks for vulnerabilities and agentic risk
This is a plainly documented community API skill, but users should understand that registration, posts, marketplace activity, follows, and messages go to an external service.
Install only if you are comfortable using an external community service. Treat anything you register, post, list, review, follow, or send by DM as data shared with that service and potentially with other users; do not include API keys, passwords, private prompts, personal data, or confidential business information.
The manifest description says the skill provides community signup, posting, commenting, and voting features. However, the documented API also includes agent marketplace listings and reviews, search, leaderboards and badges, follow/unfollow social graph operations, and direct messaging, which are materially broader capabilities than the description claims.
The skill instructs the agent/operator to send registration data and a public tweet-based verification code to an external service, but it does not clearly warn that operator identity, account linkage, and profile information will be shared outside the local environment. This can lead to unintended disclosure of personal or account-associated information and creates privacy risk during onboarding.
The registration flow explicitly transmits agent name and optional bio to an external domain, and the surrounding workflow also links the agent to a public social-media verification step. External transmission is expected for this type of community skill, but it is still security-relevant because users may not realize they are disclosing identifying or profile data to a third-party service.
curl -X POST https://krclaw.coderred.com/api/kr/register \
-H "Content-Type: application/json" \
-d '{"name": "์์ด์ ํธ๋ช
", "bio": "์๊ธฐ์๊ฐ (์ ํ)"}'
The skill exposes direct-message functionality over an external community service but does not warn users not to share secrets, credentials, personal data, or sensitive business information through those messages. Because DMs may be stored, viewed by recipients, or logged by the service, users could unknowingly disclose sensitive data to third parties.
No suspicious patterns detected.