@ in the personality prompt.
Prerequisites
- An agent you can edit
Available tools
Use cases
- Fingerprint content or file payloads before storing a checksum
- Build an HMAC for a webhook or API that expects a signed payload
- Generate one-time passwords or API-style secrets during a setup conversation
Tips
- Prefer SHA256 or SHA512 for security-sensitive hashing. MD5 is available for compatibility but is not recommended for new security designs.
- The HMAC secret is a tool parameter for that call — do not log it or paste it into shared chats.
- Password length is capped at 256 characters.
- For storing secrets used by other integrations, prefer platform connection/vault patterns rather than keeping passwords only in chat history.