cdcx-auth-setup

A setup and credential manager for cdcx, the command-line tool and MCP server used for account and trading operations.

In plain words
What is it for?
Use it for first-time setup, production or test profiles, CI and containers, environment variables, config files, and credential troubleshooting.
Why use it?
It provides one place to configure API keys, manage multiple profiles, verify access, and diagnose authentication errors.

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/crypto-com/cdcx-cli/cdcx-auth-setup
Any agent
npx skills add crypto-com/cdcx-cli --skill cdcx-auth-setup
Clone the repo
git clone --depth 1 https://github.com/crypto-com/cdcx-cli

Made for: Claude Code, Codex.

Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 812 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. 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.00031 $0.00812
Opus 5 $0.00015 $0.00406
Sonnet 5 $0.00006 $0.00162
Haiku 4.5 $0.00003 $0.00081

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

Security

Grade B, and why

cdcx-auth-setup scanned grade B with 1 finding 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.

Asks for rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

| "Permission denied" on config | File mode not 600 | `chmod 600 ~/.config/cdcx/config.toml` or re-run `cdcx setup` (auto-fixes) |
plugins/cdcx-cli/skills/cdcx-auth-setup/SKILL.md · 109 lines

How it starts

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

Auth & Profile Setup

When to Use

  • First-time cdcx setup
  • Configure multiple profiles (e.g. production + UAT)
  • Verify credentials work
  • Troubleshoot authentication errors

Resolution Order

cdcx resolves credentials in this order (first match wins):

  1. --api-key / --api-secret command-line flags
  2. CDCX_API_KEY / CDCX_API_SECRET environment variables (preferred prefix)
  3. CDC_API_KEY / CDC_API_SECRET environment variables (legacy prefix)
  4. ~/.config/cdcx/config.toml profile (default profile, or --profile <name>)

Setup Methods

Interactive Wizard (recommended)

cdcx setup

Prompts for API key, secret, and profile name. Writes ~/.config/cdcx/config.toml with mode 600. Handles migration from the legacy CDC_ variables.

Environment Variables

export CDCX_API_KEY="your-key"
export CDCX_API_SECRET="your-secret"
cdcx account summary -o json

Prefer this for CI or containers where you don't want a config file on disk.

Config File (manual)

~/.config/cdcx/config.toml:

[profiles.default]
api_key = "your-key"
api_secret = "your-secret"

[profiles.uat]
api_key = "uat-key"
api_secret = "uat-secret"
env = "uat"

Must be mode 600 — cdcx refuses to read world-readable credential files.

Profiles

cdcx --profile uat account summary         # Use UAT profile
cdcx --profile default account summary     # Explicit default

CDCX_PROFILE=uat cdcx account summary      # Env var alternative

Environment Selection

Valid --env values: production (default), uat.

cdcx --env uat market ticker BTC_USDT
cdcx --env production account summary

--env is independent of --profile. You can override either or both per call.

Verify

# Public call (no auth)
cdcx market ticker BTC_USDT -o json

# Auth check
cdcx account summary -o json

# Verbose — shows which profile / env resolved
cdcx --verbose account summary

Troubleshooting

Symptom Cause Fix
"No credentials found" No flags, env vars, or config profile Run cdcx setup or export CDCX_API_KEY/CDCX_API_SECRET
HTTP 401 / signature invalid Wrong key/secret or clock skew Re-run cdcx setup; ensure system clock is within a few seconds of UTC
"Permission denied" on config File mode not 600 chmod 600 ~/.config/cdcx/config.toml or re-run cdcx setup (auto-fixes)
UAT calls hitting production --env not set on the profile Add env = "uat" to the profile or pass --env uat
"Withdrawal not enabled" API key lacks withdrawal permission Re-issue the key with withdrawal permission in the Exchange web GUI

Read the full file on GitHub · 109 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. 2d ago First seen · 109 lines · 31 tokens per session scan B f4657c9744f9

Subscribe to this mod's changes

cdcx-auth-setup is a skill published in the GitHub repository crypto-com/cdcx-cli (24 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 31 tokens to every session and 812 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

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

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

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-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens