国内Minimax Coding Plan订阅计划用量查询

Monitor Minimax Coding Plan usage to stay within API limits. Fetches current usage stats and provides status alerts.

Before installing or running this skill: (1) Inspect minimax-coding-plan-usage.sh line-by-line — confirm it only calls the documented Minimax endpoint and does not read unrelated files, call other domains, or exfiltrate data. (2) Prefer providing a scoped API key with minimal permissions; avoid using long-lived or broad keys. (3) Store secrets securely (not in a repo); if you must use a .env file, add it to .gitignore. (4) Ask the publisher why the registry metadata omits the required env vars and request explicit declaration of required credentials. (5) If unsure, run the script in a sandboxed environment or with network monitoring to observe outbound requests.

Type: OpenClaw Skill Name: minimax-coding-plan-usage Version: 1.0.0 The skill is classified as suspicious primarily due to the `minimax-coding-plan-usage.sh` script sourcing a `.env` file from `../../.env`. This path suggests it attempts to load a global OpenClaw configuration file (e.g., `~/.openclaw/.env`), which contradicts the `SKILL.md` instructions to create a `.env` file in the skill's local directory. While the script only explicitly uses `MINIMAX_CODING_API_KEY` and `MINIMAX_GROUP_ID`, loading a potentially global `.env` file means all variables within it would be exposed to the script's environment, representing a broader permission than necessary and a potential information exposure risk, even without clear malicious intent to exfiltrate them. The network calls are to a legitimate Minimax API endpoint (platform.minimax.com) and do not show signs of data exfiltration to unauthorized destinations.