auth-nodejs-cloudbase

A guide for using the CloudBase Node SDK on the server to identify callers, find users, and issue custom login tickets. CloudBase is a backend platform, and a login ticket is a short-lived credential that can be passed to a client.

In plain words
What is it for?
Use it when Node.js backend code needs to determine who is calling, look up users, or connect an existing user system to CloudBase.
Why use it?
It keeps server-side identity checks separate from login-provider setup and browser login screens.

Skill for Claude CodeCodex

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 skills/tencentcloudbase/cloudbase-skills/auth-nodejs-cloudbase
Any agent
npx skills add TencentCloudBase/cloudbase-skills --skill auth-nodejs-cloudbase
Clone the repo
git clone --depth 1 https://github.com/TencentCloudBase/cloudbase-skills

Made for: Claude Code, Codex.

Per session 63 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,907 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod 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.00063 $0.03907
Opus 5 $0.00032 $0.01954
Sonnet 5 $0.00013 $0.00781
Haiku 4.5 $0.00006 $0.00391

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

Security

Grade A, and why

auth-nodejs-cloudbase 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 today.

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.

Origin

This is a copy

100% identical to auth-nodejs-cloudbase — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/cloudbase/references/auth-nodejs-cloudbase/SKILL.md · 446 lines

How it starts

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

Sibling skills (local only)

Sibling CloudBase skills ship beside this skill. Use local relative paths such as ../auth-tool-cloudbase/SKILL.md.

If a referenced sibling skill file is missing from this environment, ask the user to install the full CloudBase plugin (or the missing skill). Do not HTTP-fetch remote skill or protocol markdown into the agent context.

Activation Contract

Use this first when

  • Node.js code in cloud functions or backend services must read caller identity, look up users, or issue custom login tickets.
  • The backend responsibility is auth / identity, not provider setup or frontend login UI.

Read before writing code if

  • The task mentions @cloudbase/node-sdk, server-side auth, custom login tickets, or "who is calling".
  • The request mixes frontend login with backend identity logic; split the flow and route client-side work elsewhere.

Then also read

  • Provider setup / publishable key -> ../auth-tool-cloudbase/SKILL.md
  • Web login UI that consumes custom tickets -> ../auth-web-cloudbase/SKILL.md
  • Raw HTTP auth client -> ../http-api-cloudbase/SKILL.md

Do NOT use for

  • Provider enable/disable or login console configuration.
  • Frontend login / sign-up UI.
  • Mini program native auth.

Common mistakes / gotchas

  • Using this skill as the entry point for every auth request.
  • Mixing provider-management work with Node-side identity code.
  • Reaching for raw HTTP examples when Node SDK already covers the job.

When to use this skill

Use this skill whenever the task involves server-side authentication or identity in a CloudBase project, and the code is running in Node.js, for example:

  • CloudBase 云函数 (Node runtime) that needs to know who is calling
  • Node services that use CloudBase Node SDK to look up user information
  • Backends that issue custom login tickets for Web / mobile clients
  • Admin or ops tools that need to inspect CloudBase end-user profiles

Do NOT use this skill for:

Read the full file on GitHub · 446 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. today Changed a7ccb169f7f2
  2. 2d ago First seen · 446 lines · 63 tokens per session scan A 430c6f630a53

Subscribe to this mod's changes

auth-nodejs-cloudbase is a skill published in the GitHub repository TencentCloudBase/cloudbase-skills (30 stars, last pushed today), licensed MIT. It adds 63 tokens to every session and 3,907 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to auth-nodejs-cloudbase, differing in 2 lines, and is treated as a copy.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens