Monzo

Access Monzo bank account - check balance, view transactions, manage pots, send feed notifications. For personal finance queries and banking automation.

This skill appears coherent for connecting OpenClaw to Monzo. Things to consider before installing: - Protect MONZO_KEYRING_PASSWORD: prefer injecting it via a secrets manager or environment at runtime, not by putting it in openclaw.json in plaintext. If you must store it in a file, restrict permissions (chmod 600) and avoid committing to version control. - Credentials on disk: OAuth client secret, access and refresh tokens are encrypted with AES-256-CBC (PBKDF2 100k) and saved under ~/.openclaw/credentials/monzo.json. If an attacker gains OS-level access (root, malware, keylogger), credentials can be compromised — follow the README's advice to revoke the OAuth client immediately in that case. - Webhooks: only register URLs you control and use HTTPS. An attacker-controlled webhook URL would receive transaction notifications. - Non-interactive/automation: the setup script supports providing client secrets and auth codes on the command line — avoid putting secrets in shell history or logs; prefer non-logged secret injection. - Review the bundled scripts yourself (they are included) or run them in a controlled environment first. If you follow the guidance above (use secrets manager, restrict file permissions, run on machines you control, and review webhook endpoints), the skill is coherent with its stated purpose and can be used safely for Monzo automation.

Type: OpenClaw Skill Name: monzo Version: 1.0.2 The OpenClaw Monzo skill is well-documented and transparent, adhering to good security practices. Credentials are encrypted at rest using AES-256-CBC with PBKDF2, and the setup process includes OAuth state validation to prevent CSRF. The documentation (`SKILL.md`, `README.md`, `SECURITY.md`) explicitly details the threat model, warns about the `MONZO_KEYRING_PASSWORD` being visible in process environments on multi-user systems, and advises caution with webhook URLs. All code aligns with the stated purpose of Monzo banking operations, without any evidence of intentional data exfiltration to unauthorized endpoints, malicious execution, persistence mechanisms, or prompt injection attempts against the agent.