Security audit
Security checks across malware telemetry and agentic risk
This is a transparent notes client, but it gives an agent password-backed access to read, edit, and delete a live notes account without strong guardrails.
Install only if you control the configured Alexandrie account and want an agent to access it. Treat it as permission to read, create, update, and delete private notes; require explicit confirmation before update or delete actions, protect the .env file, and run logout or remove the /tmp cookie files when finished.
USER_ID_FILE="/tmp/alexandrie_user_id"
# Load password from env
source /home/eth3rnit3/clawd/.env 2>/dev/null || true
PASSWORD="${ALEXANDRIE_PASSWORD:-}"
if [[ -z "$PASSWORD" ]]; then- `GET /nodes/search?q=query` - Search nodes - `POST /nodes` - Create node - `PUT /nodes/:nodeId` - Update node - `DELETE /nodes/:nodeId` - Delete node ### Authentication JWT token stored in cookies after login (`/tmp/alexandrie_cookies.txt`).
63/63 vendors flagged this skill as clean.
No suspicious patterns detected.