Skip to main content

subme-admin

Manage Sub2API admin APIs for accounts, groups, proxies, error passthrough rules, TLS fingerprint profiles, imports, exports, batch updates, and raw administrator API calls. Use when the user mentions Sub2API, admin API keys, account management, bulk account import/export, keeping or deleting accounts, refreshing accounts, clearing errors, CRS sync, or managing Sub2API backend settings through the admin API.

Datos de origen

Repositorio
telagod/subme
Última actividad en el origen
18 de junio de 2026 a las 04:06
Idioma detectado de SKILL.md
inglés
Estrellas
0
Forks
0

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

Explorador de archivos
4 archivos

Mostrando SKILL.md

SKILL.md
Instrucciones de origen · Vista previa de solo lectura
name
subme-admin
description
Manage Sub2API admin APIs for accounts, groups, proxies, error passthrough rules, TLS fingerprint profiles, imports, exports, batch updates, and raw administrator API calls. Use when the user mentions Sub2API, admin API keys, account management, bulk account import/export, keeping or deleting accounts, refreshing accounts, clearing errors, CRS sync, or managing Sub2API backend settings through the admin API.
# Sub2API Admin Use the bundled CLI instead of ad hoc `curl`. Run examples from this skill directory. ```bash export SUBME_BASE_URL='https://your-subme-host' export SUBME_ADMIN_API_KEY='<admin api key>' node ~/.codex/skills/subme-admin/scripts/subme-admin.js accounts list ``` For all commands and payload examples, read [references/admin-cli.md](references/admin-cli.md). ## Workflow 1. Reuse `SUBME_BASE_URL` and `SUBME_ADMIN_API_KEY` from the environment. 2. Run read-only commands first: `accounts list`, `accounts get <id>`, `groups all`, or `proxies all`. 3. Before destructive or bulk writes, print the target account names and IDs. 4. Execute the write command only after the target set is clear. 5. Run a follow-up read command to verify the result. ## Common Commands ```bash node ~/.codex/skills/subme-admin/scripts/subme-admin.js accounts list --page-size 20 node ~/.codex/skills/subme-admin/scripts/subme-admin.js accounts get 40 node ~/.codex/skills/subme-admin/scripts/subme-admin.js accounts usage 40 node ~/.codex/skills/subme-admin/scripts/subme-admin.js accounts set-schedulable 40 true node ~/.codex/skills/subme-admin/scripts/subme-admin.js accounts bulk-update --ids 40,39 --json '{"concurrency":10}' node ~/.codex/skills/subme-admin/scripts/subme-admin.js error-rules list node ~/.codex/skills/subme-admin/scripts/subme-admin.js tls-profiles list ``` ## Safety Notes - Authentication uses only `x-api-key`. - If the API returns `INVALID_ADMIN_KEY`, ask the user to regenerate the admin API key. - `accounts export` includes credentials and tokens. Prefer `--file` and avoid printing exports in chat. - Redeem code create/redeem commands should use `--idempotency-key` for payment or recharge workflows. - For uncertain or newly added backend APIs, use `api <METHOD> <admin-path>` after a read-only check.
Ver en GitHub