imsg-rpc

This skill is an operational guide to run a high-privilege macOS agent that reads the user message database and exposes it over a local Unix socket. Functionality is coherent with its stated purpose (bridging iMessage to a gateway) and requires FDA and code-signing. There is no evidence in the provided fragment of remote download-and-execute, third-party credential forwarding, or obfuscated payloads. However, the design inherently carries significant privacy and supply-chain risk: the imsg binary runs with broad filesystem access, the docs encourage creating/trusting a local code-signing certificate (example passphrase present), and the socket location in /tmp could allow other local processes to connect if permissions are not tightly controlled. I assess low probability of intentional malware in this fragment (malware: 0.05) but a moderate overall security risk (securityRisk: 0.55) because of high-privilege access, potential for credential misuse, and local data-exfiltration paths. Operators should ensure the signing key is protected, avoid using example passphrases in production, restrict socket permissions, and audit the gateway consumer process before running this setup on sensitive systems.