SKILLEMALL.ai

CC minimax-token-plan-monitor

MiniMax Token Plan 用量监控 — 自动查询本周/5小时窗口用量、套餐余量、剩余调用次数及重置时间。支持 QQ/Discord/Telegram 多通道通知,可配置告警阈值。触发词:minimax额度查询、token plan用量、本周用量、剩余次数、订阅状态、minimax coding plan、minimax配额。

ClawHub Agent Skills author: bbzhi177 v1.2.0 MIT-0 9 files · 5 scripts body ≈ 508 tokens Open the sourceclawhub.ai↗ analyzed 11 d ago

MiniMax Token Plan 用量监控 — 自动查询本周/5小时窗口用量、套餐余量、剩余调用次数及重置时间。支持 QQ/Discord/Telegram 多通道通知,可配置告警阈值。触发词:minimax额度查询、token plan用量、本周用量、剩余次数、订阅状态、minimax coding…

As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

ProcedureDiscordTelegramSoftware developmenttype and topics are labelled automatically from the skill text
JSON
Technical rating
C
82/100
safety, quality, tests
Safety 60%
90
Quality 40%
69
Run on models
none yet
Process rating
C
53/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Secrets in code medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The files contain someone else's key or token. If it is live, your agent will call third-party services under a stranger's identity; if it was revoked, the skill's scripts simply fail. Such a key often arrives with the author's whole workspace, personal data included.

For the author

The key is visible to everyone who downloaded the skill and has likely been copied by catalog-scanning bots already. Revoke it now, check bills and access logs, then reissue.

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 6

✓ No critical or high findings

Medium and low: 6
  • medium Secrets in code secret-labelled-token scripts/cron_send.js:8
    Labelled token / key literal (vendor format unknown — verify it is not a live credential)
    const authToken = '8d9c…8fd';
  • low Secrets in code secret-high-entropy-token scripts/package-lock.json:73
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "integrity": "sha5…bKX+KS9G…yMA/NhKJ…RGz/Q==",
    quoted
  • low Secrets in code secret-high-entropy-token scripts/package-lock.json:137
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "integrity": "sha5…Wwy+ghLE…vfU/YnxW…fdg==",
    quoted
  • low Secrets in code secret-high-entropy-token scripts/package-lock.json:171
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "integrity": "sha5…DYr+NSUK…Itc/irNR…37y+AMujNyNtG+1Rggw==",
    quoted
  • low Secrets in code secret-high-entropy-token scripts/package-lock.json:213
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "integrity": "sha5…bgK+BO66q+ZpKq…RhN+7lnv…m9g==",
    quoted
  • low Secrets in code secret-high-entropy-token scripts/package-lock.json:248
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "integrity": "sha5…2BV+FY5ZFezP/ypmwayk68+NzzA…NFD/uUmBJuGoXw==",
    quoted

Files scanned: 9. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 53/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 100Tools and files. No external tools needed
  • 100Steps. 8 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 508 tokens
  • 100Running it twice. No mutating operations

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • -34 of 5 scripts are never mentioned in SKILL.md
  • +1No license
  • +2Single-language instructions
  • +3Description length 169: enough signal without eating the budget
  • +4Structure: 12 headings
  • +3Step-by-step instructions: 8 items
  • +4Has examples (6 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.

External checks

ClawHub: suspicious
The skill largely matches a token-usage scraper but contains hardcoded account credentials and local gateway tokens, plus mismatches between the README and the code — these inconsistencies could lead to credential misuse or unexpected access to the host OpenClaw service.
LLM: suspicious (medium) · 4 Apr 2026