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 agentmods add skills/coralogix/cx-cli/cx-platform-adminnpx skills add coralogix/cx-cli --skill cx-platform-admingit clone --depth 1 https://github.com/coralogix/cx-cliWrote 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/coralogix/cx-cli/cx-platform-admin)<a href="https://agentmods.dev/skills/coralogix/cx-cli/cx-platform-admin"><img src="https://agentmods.dev/badge/skills/coralogix/cx-cli/cx-platform-admin.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00133 | $0.01863 |
| Opus 5 | $0.00067 | $0.00932 |
| Sonnet 5 | $0.00027 | $0.00373 |
| Haiku 4.5 | $0.00013 | $0.00186 |
Grade A, and why
cx-platform-admin 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 4d 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 — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Platform Admin Skill
Use this skill for managing access, authentication, and authorization in Coralogix. It covers API key management, role and scope definitions, user administration, team groups, and IP access restrictions.
Destructive Operation Safety
All write operations (create, update, delete, set-idp, set-active, set-status) require interactive confirmation. The CLI will prompt before executing. To skip the prompt in scripts, pass --yes.
IMPORTANT: NEVER pass --yes without explicit user approval. Before executing any write operation:
- Describe the exact operation to the user (what will be created/modified/deleted)
- Wait for the user to confirm
- Only then execute with
--yes
Read-only operations (list, get, search, system, sp-params, send-data-keys) do not require confirmation and can be run freely.
Read-Only Mode
Use --read-only (or CX_READ_ONLY=1) to block all write operations at the CLI level. This is useful for safe exploration - you can query any IAM resource without risk of accidental modifications.
Agent Mode
When running inside an AI agent (Claude Code, Cursor, Codex, etc.), cx automatically detects the agent environment and fails fast on write operations instead of hanging on a stdin prompt. The error message instructs you to get user confirmation first, then re-run with --yes.
CLI Commands
API Keys
| Command | Purpose |
|---|---|
cx iam api-keys list |
List all API keys |
cx iam api-keys get <id> |
Get a single API key |
cx iam api-keys create --from-file |
Create an API key |
cx iam api-keys update --from-file <id> |
Update an API key |
cx iam api-keys delete <id> |
Delete an API key |
cx iam api-keys send-data-keys |
List send-data API keys |
cx iam api-keys admin list |
List all team members' keys |
cx iam api-keys admin delete --ids <id1> <id2> |
Bulk delete keys |
cx iam api-keys admin set-status --ids <id1> --active true/false |
Activate/deactivate keys |
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.
- 4d ago First seen · 202 lines · 133 tokens per session scan A bd5f47541b46
cx-platform-admin is a skill published in the GitHub repository coralogix/cx-cli (116 stars, last pushed today), licensed Apache-2.0. It adds 133 tokens to every session and 1,863 once invoked, about $0.0007 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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.
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…