Mog

Microsoft Ops Gadget — CLI for Microsoft 365 (Mail, Calendar, Drive, Contacts, Tasks, Word, PowerPoint, Excel, OneNote).

What to consider before installing/using this skill: - Source verification: the skill bundle includes full Go source but the registry metadata gives no homepage and an opaque owner ID. Prefer to install only from a known upstream (GitHub repo or the project's official release). If you plan to use it, fetch the code from the upstream repository (if available) and build locally rather than executing pre-built artifacts from an unknown source. - Credentials and tokens: the CLI uses OAuth device flow and will store tokens in ~/.config/mog/tokens.json (or OS keyring). Create and use your own Azure AD App (client id) as instructed; do not reuse a public/shared client id. Expect the CLI to request wide Microsoft Graph delegated permissions (Mail.ReadWrite, Files.ReadWrite.All, Calendars.ReadWrite, etc.) — grant only what you trust. - Metadata mismatch: registry metadata lists no required env vars/config paths, but SKILL.md and code reference MOG_CLIENT_ID and local config files. Treat the metadata as incomplete and verify the declared requirements yourself. - Inspect the code for hidden behavior: the pre-scan flagged unicode control characters in SKILL.md — view the raw files to confirm there are no hidden prompt injection strings or obfuscated endpoints. Also review internal/graph/client.go (not fully shown here) to confirm the HTTP endpoints are Microsoft Graph APIs rather than unexpected servers. - Build and run locally: if you decide to use the tool, clone the repository and build it locally (go build/go install) and run tests. Running on your machine gives you more control over what is executed and lets you audit the binary and source before trusting it with OAuth scopes. - Least privilege: when registering your Azure AD app, grant only the delegated permissions you need, and consider creating a test account with limited data for initial evaluation. If you want, I can: - Extract and show any remaining unreviewed files (graph client code) for a closer look, - Show commands to build/run the project locally and inspect tokens/config, - Highlight exact locations of any non-printing/unicode-control characters found in SKILL.md.

Type: OpenClaw Skill Name: mogcli Version: 0.3.1 The OpenClaw AgentSkills skill bundle 'mogcli' appears benign. The code and documentation consistently describe a legitimate CLI tool for Microsoft 365, with all network communications directed to official Microsoft Graph and OAuth endpoints. File system operations are confined to user-specified paths for uploads/downloads and standard configuration files in `~/.config/mog/` with appropriate permissions. While the requested Azure AD permissions are broad (e.g., `Files.ReadWrite.All`), they align with the comprehensive functionality advertised by the tool. No evidence of intentional harmful behavior, obfuscation, or prompt injection attempts against the AI agent to perform unauthorized actions was found in any of the analyzed files, including `SKILL.md` and `internal/cli/ai_help.go`.