CloudBase AI Toolkit is an integration layer that lets AI coding tools use Tencent CloudBase as an application backend, including databases, authentication, functions, storage, and deployments. Developers use it to have coding agents build and operate CloudBase-backed applications through skills, plugins, commands, and chat-accessible tools. The catalogue entries are the toolkit’s own skills, agents, hooks, plugins, rules, instructions, and MCP tools.
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.
npx skills add TencentCloudBase/CloudBase-AI-Toolkit --skill api-contract-reviewgit clone --depth 1 https://github.com/TencentCloudBase/CloudBase-AI-ToolkitWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/tencentcloudbase/cloudbase-ai-toolkit/api-contract-review)<a href="https://agentmods.dev/skills/tencentcloudbase/cloudbase-ai-toolkit/api-contract-review"><img src="https://agentmods.dev/badge/skills/tencentcloudbase/cloudbase-ai-toolkit/api-contract-review/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/tencentcloudbase/cloudbase-ai-toolkit/api-contract-review"><img src="https://agentmods.dev/badge/skills/tencentcloudbase/cloudbase-ai-toolkit/api-contract-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00054 | $0.01267 |
| Opus 5.5 | $0.00022 | $0.00507 |
| Sonnet 5.5 | $0.00011 | $0.00253 |
| Haiku 4.5 | $0.00005 | $0.00127 |
Grade A, and why
api-contract-review 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 1mo ago.
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.
How it starts
The opening of the file, as written. The whole thing — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Contract Review
Review CloudBase cloud API integrations for contract correctness before the repository ships stale, guessed, or undocumented behavior.
When to use this skill
Use this skill when you need to:
- Review CloudBase cloud API wrappers or MCP tools for outdated or incorrect action or interface names
- Check whether request parameters, casing, nesting, or request shape drifted away from documentation
- Audit whether a CloudBase API change is backed by the right contract tests
- Run a periodic API correctness review before opening corrective PRs
- Separate confirmed contract bugs from vague "maybe this API changed" speculation
Do NOT use for:
- General code smell review without a contract-correctness question
- Regular SDK usage that does not touch CloudBase control-plane or documented API contracts
- Guessing undocumented behavior from naming intuition
- Shipping a fix when the documentation still does not support the proposed action or parameter shape
Workflow
Phase 1 — Scope and evidence
- Read
references/review-checklist.mdfirst. - Identify the review surface:
mcp/src/tools/*- related tests
- generated action metadata
- user-facing docs that describe the same API behavior
- Record the exact action, interface, or payload being reviewed before forming conclusions.
Phase 2 — Documentation-first verification
Before judging any implementation, you must read the relevant official documentation first.
Required entry points:
- CloudBase API overview:
https://cloud.tencent.com/document/product/876/34809 - Dependency-resource API docs when relevant:
https://cloud.tencent.com/document/product/876/34808 - CloudBase Manager SDK docs before approving direct Cloud API usage:
https://docs.cloudbase.net/api-reference/manager/node/introduction
Verify the documented contract, not your memory:
- exact action or interface name
- required and optional parameters
- parameter casing and nesting
- request shape
- auth model and caller context
- response shape, task model, and documented limits
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 138 lines · 54 tokens per session scan A 13b00588a9db
api-contract-review is a skill published in the GitHub repository TencentCloudBase/CloudBase-AI-Toolkit (1,138 stars, last pushed today), licensed MIT. It adds 54 tokens to every session and 1,267 once invoked, about $0.0002 per session on Opus 5.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.
Other skills, from other repositories
Baseline Security Checks
Check common security risks in application code (SQLi, XSS, secrets, open redirect).
platform-apex-generate
Primary Apex authoring skill for class generation, refactoring, and review. ALWAYS ACTIVATE when the user mentions Apex, .cls, triggers, or asks to create/refactor a class (service, selector, domain, batch, queueable, schedulable, invocable, DTO, utility, interface, abstract, exception, REST resource). Use this skill…
horse-app-structure
Guide for setting up Horse applications, bootstrap program (.dpr), basic console initialization, and registering modules.
horse-ssl-tls
Guide to enabling SSL/TLS, configuring HTTPS, handling certificates, and securing transport layers.
flow-next-impl-review
Carmack-level implementation review of changes via the configured backend. Use when asked to review code or a diff in a flow-next repo.
ring:migrating-to-lib-observability
Migrating a Lerian Go app off lib-commons observability imports (deprecated shims or removed APIs) to lib-observability via a fixed mapping table, then bumps go.mod and validates the build; ring:backend-go applies the edits. Covers log/zap/runtime/assert, opentelemetry/tracing, HTTP middleware, context helpers, and…