auth-wechat-miniprogram

A guide to native user identity in WeChat Mini Programs, lightweight apps that run inside WeChat, with CloudBase cloud services.

In plain words
What is it for?
Use it when handling OPENID or UNIONID, checking wx.cloud identity, or identifying users inside CloudBase functions.
Why use it?
It clarifies how WeChat identifies callers and avoids treating a Mini Program like a website with its own login page.

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-ai-toolkit/auth-wechat-miniprogram
Any agent
npx skills add TencentCloudBase/CloudBase-AI-Toolkit --skill auth-wechat-miniprogram
Clone the repo
git clone --depth 1 https://github.com/TencentCloudBase/CloudBase-AI-Toolkit

Made for: Claude Code, Codex.

Per session 54 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,163 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.00054 $0.01163
Opus 5 $0.00027 $0.00581
Sonnet 5 $0.00011 $0.00233
Haiku 4.5 $0.00005 $0.00116

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

Security

Grade A, and why

auth-wechat-miniprogram 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 2d 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.

Origin

Copies of this mod

2 near-identical copies found in the catalogue:

config/.claude/skills/auth-wechat-miniprogram/SKILL.md · 131 lines

How it starts

The opening of the file, as written. The whole thing — 131 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

  • The task is about WeChat Mini Program auth behavior, wx.cloud identity, OPENID / UNIONID, or how a mini program caller is identified in CloudBase.
  • The project is a CloudBase mini program and the auth question is about native mini program identity rather than provider configuration.

Read before writing code if

  • The request mentions mini program login, user identity in cloud functions, or wx.cloud auth assumptions.
  • The user expects a Web-style login page or explicit token exchange in a mini program; route them back to native mini program auth behavior.

Then also read

  • Mini program project implementation -> ../miniprogram-development/SKILL.md
  • Cloud function implementation -> ../cloud-functions/SKILL.md

Do NOT use for

  • Web-based WeChat login or Web auth UI.
  • Provider enable/disable or auth console setup.
  • Generic Node-side auth flows outside mini program identity handling.

Common mistakes / gotchas

  • Generating a Web-style login page for a wx.cloud mini program.
  • Treating mini program auth as a provider-configuration problem.
  • Forgetting that caller identity is injected in cloud functions automatically.

When to use this skill

Use this skill for WeChat Mini Program (小程序) authentication in a CloudBase project.

Use it when you need to:

  • Implement identity-aware WeChat Mini Program flows with CloudBase
  • Access user identity (openid, unionid) in cloud functions
  • Understand how WeChat authentication integrates with CloudBase
  • Build Mini Program features that require user identification

Key advantage: WeChat Mini Program authentication with CloudBase is seamless and automatic - no complex OAuth flows needed. When a Mini Program calls a cloud function, the user's openid is automatically injected and verified by WeChat.

Read the full file on GitHub · 131 lines

Files

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.

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. 2d ago First seen · 131 lines · 54 tokens per session scan A f0b3e2431575

Subscribe to this mod's changes

auth-wechat-miniprogram is a skill published in the GitHub repository TencentCloudBase/CloudBase-AI-Toolkit (1,087 stars, last pushed 2d ago), licensed MIT. It adds 54 tokens to every session and 1,163 once invoked, about $0.0003 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.