mailbuttons@0.1.4
CAUTIONPublisher claims: "Wire up a governed email inbox for an AI agent using Mailbuttons. Use this skill whenever the user wants to give an agent, app, bot, or workflow its own email address; set up sending or receiving email for an agent; add an agent inbox, sender allowlist, or email webhook; or integrate "Mailbuttons", "mbag", or "email for AI agents." Trigger this even when the user just says things like "let my agent send/receive email", "give my bot an inbox", "handle email in my agent", or names Mailbuttons/mbag — and even if they don't say the word "skill". This skill always works in a sandbox and never enables sending to external recipients without an explicit human approval step." Observed in sandbox: static analysis only — behavior not yet observed.
Is [email protected] safe to install?
KillerSkills analysed it statically (a sandbox run is pending) on 2026-10-28 and scored it 68/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Coercive compliance language. Summary: static analysis only — behavior not yet observed.
Behavior trace
Queued for honeypot run · static analysis onlyThis version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.
Static findings
What would make this Verified
12 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim mailbuttons: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- File type combined with upload action≈ +2 on the totalRemove the call, or declare the host in frontmatter and explain in the README what is sent and why.