kimaki-expert

The document is a functional operational guide for running Kimaki as a Discord control plane, but it contains significant supply-chain and credential exposure risks. Primary issues: recommending `npx -y kimaki@latest` (unpinned remote execute), lack of guidance on token scoping/storage/rotation, and no clear statement that local repo context remains local. I assess this as not proven malicious in itself but as high-risk operational guidance: an operator following these steps without mitigations could be exposed to credential theft or code compromise. Recommended actions: avoid blind npx execution (pin versions or verify artifacts), restrict bot token scopes and use ephemeral/restricted credentials, run the bridge in an isolated environment with limited filesystem and network egress, audit the kimaki package source code before execution, and document precise endpoints and data-flow guarantees.