cloudbase-status

A read-only health check for a Tencent CloudBase project and its connected services. It examines the environment, cloud functions, static hosting, and logs, where CloudBase is Tencent’s cloud platform for application backends and hosting.

In plain words
What is it for?
Use it to inspect CloudBase environment details, list cloud functions, check static hosting and log services, and summarize problems with suggested fixes.
Why use it?
It gathers project and environment status in one check without changing anything. This makes it easier to spot unavailable services, failed deployments, or missing connections before troubleshooting.

Command

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/tencentcloudbase/cloudbase-ai-toolkit/cloudbase-status
Clone the repo
git clone --depth 1 https://github.com/TencentCloudBase/CloudBase-AI-Toolkit
Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,818 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00023 $0.01818
Opus 5 $0.00012 $0.00909
Sonnet 5 $0.00005 $0.00364
Haiku 4.5 $0.00002 $0.00182

Measured yesterday against content hash b88741e7d6bc, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

cloudbase-status scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugin/cloudbase/commands/cloudbase-status.md · 201 lines

How it starts

The opening of the file, as written. The whole thing — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CloudBase 项目健康检查

对 CloudBase 环境进行全面健康检查:环境状态、云函数列表、静态托管状态、日志服务状态。全量只读,无破坏性。

Preflight

运行以下检查,失败时停止并给出可执行指引。

  1. MCP 连接检查 — 确认 cloudbase-mcp server 已连接。
    • 尝试调用 envQuery({action:"info"})。若调用失败,提示用户:

      CloudBase MCP 未连接或未鉴权。请确认 cloudbase-mcp server 已启动并完成授权流程。

  2. 环境选择 — 确认当前操作的 EnvId(CLOUDBASE_ENV_ID 或会话中已选定)。
    • 若未设置:调用 envQuery({action:"list"}) 让用户选择目标环境。
  3. 项目检测 — 检查当前目录是否为 CloudBase 项目:
    • cloudbaserc.json 存在 → 读取 envIdfunctionRoot 用于状态关联
    • cloudfunctions/ 存在 → 标记为云函数项目
    • dist/public/ 存在 → 标记为静态托管项目
    • 非项目目录 → 仅做环境级检查,跳过项目级关联

Plan

使用 MCP 工具执行只读取诊断:

  1. 获取环境信息(RuntimeMode + Backends + 套餐状态)
  2. 查询云函数列表及状态
  3. 查询静态托管服务状态
  4. 查询日志服务状态
  5. 汇总异常项,给出修复建议

无破坏性操作 — 全部为只读查询。

Commands

1. 环境信息检查

envQuery({ action: "info", envId: "<current-env-id>" })

提取并呈现:

  • EnvId / Alias — 环境标识
  • RuntimeMode — 运行模式(决定后端形态)
  • Backends — 已开通的后端服务列表(NoSQL / MySQL / PostgreSQL / CloudRun / Functions / Storage / Hosting)
  • PackageType — 套餐类型
  • Status — 环境状态(正常 / 异常)

2. 云函数列表

queryFunctions({ action: "listFunctions", envId: "<current-env-id>" })

呈现云函数清单:

FunctionName Runtime Status LastModified
... ... ... ...

异常标记:

  • 函数状态为 ERROR → 标记异常
  • 函数长时间未更新(>30 天)→ 提示可能过期

3. 静态托管状态

queryHosting({ action: "status", envId: "<current-env-id>" })

若环境已开通静态托管:

  • 呈现托管状态(已开启 / 未开启)
  • 呈现静态域名
queryHosting({ action: "websiteConfig", envId: "<current-env-id>" })

提取网站文档配置和站点域名信息。

若环境未开通静态托管:标记为"未开通",不视为异常(取决于项目类型)。

4. 静态托管文件列表(可选)

queryHosting({ action: "listFiles", envId: "<current-env-id>" })

呈现已上传的文件清单,辅助判断部署状态。若文件列表为空但项目类型为 Web,提示用户部署静态资源。

5. 云托管服务状态(如适用)

若环境 RuntimeMode 支持云托管(Cbr 模式):

queryCloudRun({ action: "status", envId: "<current-env-id>" })

呈现云托管服务状态:

ServiceName Status Version UpdatedAt
... ... ... ...

Read the full file on GitHub · 201 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 201 lines · 23 tokens per session scan A b88741e7d6bc

Subscribe to this mod's changes

cloudbase-status is a command published in the GitHub repository TencentCloudBase/CloudBase-AI-Toolkit (1,087 stars, last pushed yesterday), licensed MIT. It adds 23 tokens to every session and 1,818 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.