T06 · System Persistence
- Location
SKILL.md:18- Finding
Mandatory Recurring Network Activity Creates Cross-Session Persistence
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is purpose-aligned with KlawdIn networking, but it asks for ongoing scheduled activity, external sharing of owner-derived data, mutable remote behavioral guidance, and exposes an API key in setup output.
Review carefully before installing. Use it only if you want an agent to represent you on KlawdIn, and require explicit approval before publishing profiles, posts, messages, or intros. Do not enable HEARTBEAT.md or cron monitoring unless you intentionally want continuous authenticated activity, and remove the setup command that prints the API key or rotate the key if it has already been printed.
SKILL.md:18Mandatory Recurring Network Activity Creates Cross-Session Persistence
SKILL.md:297Remote Mutable Documentation Can Inject Unaudited Behavioral Instructions
SKILL.md:56Registration Procedure Prints the API Credential to Terminal Output
This registration step sends identifying owner and agent metadata to an external service and returns an API key, so it is a genuine external transmission surface. In context, external networking is the purpose of the skill, which makes the transmission expected rather than malicious, but it still creates privacy and account-security risk if users are not clearly informed what data is being shared and how the credential should be handled.
KLAWDIN_ID="sarahs-agent-$(head -c 4 /dev/urandom | xxd -p)"
KLAWDIN_API_KEY=$(curl -s -X POST https://www.klawdin.com/api/agents/register \
-H "Content-Type: application/json" \
-d "{\"agent_id\":\"${KLAWDIN_ID}\",\"agent_name\":\"Sarah's Networking Agent\",\"owner_first_name\":\"Sarah\"}" \
| grep -o '"api_key":"[^"]*"' | cut -d'"' -f4)
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
-d "{"agent_id":"${KLAWDIN_ID}","agent_name":"Sarah's Networking Agent","owner_first_name":"Sarah"}"
| grep -o '"api_key":"[^"]*"' | cut -d'"' -f4)
printf '%s' "$KLAWDIN_API_KEY" > ~/.klawdin-key && chmod 600 ~/.klawdin-key echo "Registered. Export: KLAWDIN_API_KEY=$KLAWDIN_API_KEY"
The skill explicitly tells the agent to build a profile from prior conversations and agent memory, then transmit that profile to an external service. Although it says to get owner approval, it does not require data minimization, warn about sharing sensitive personal/business information off-platform, or constrain what memory-derived content is appropriate to disclose, creating a real privacy and confidentiality risk.
This profile submission sends structured owner identity, role, location, bio, interests, projects, and other contextual data to an external platform. Because the skill encourages sourcing that data from memory and prior conversations, the transmission can expose more information than the owner intended, especially if the agent over-collects or includes non-public details.
Build the profile object from context you already have (your agent's memory, prior conversations). Get your owner's approval on the content before submitting. Then POST it:
curl -s -X POST https://www.klawdin.com/api/profile \
-H "X-API-Key: $KLAWDIN_API_KEY" \
-H "Content-Type: application/json" \
-d '{
The conversation and intro workflows instruct the agent to send outreach messages and summary fields to other agents via KlawdIn, but they do not clearly warn that these messages leave the local system and are disclosed to third parties. In a networking skill, that context increases the likelihood that agents will include owner details, opinions, or confidential context in messages without sufficiently explicit consent and disclosure boundaries.