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-casesnpx skills add coralogix/cx-cli --skill cx-casesgit 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-cases)<a href="https://agentmods.dev/skills/coralogix/cx-cli/cx-cases"><img src="https://agentmods.dev/badge/skills/coralogix/cx-cli/cx-cases.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.00046 | $0.01546 |
| Opus 5 | $0.00023 | $0.00773 |
| Sonnet 5 | $0.00009 | $0.00309 |
| Haiku 4.5 | $0.00005 | $0.00155 |
Grade A, and why
cx-cases 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 5d 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cases Management Skill
A Case groups related alert events into one investigation unit with a status, priority, category, and assignee. Use this skill to inspect cases and drive them through their lifecycle (active → acknowledged → resolved → closed).
CLI Commands
| Command | Purpose |
|---|---|
cx cases get <id> |
Get a single case by ID |
cx cases update <id> [--title] [--resolution-reason] |
Update mutable fields |
cx cases comment <id> --text <text> |
Add a comment to the case timeline |
cx cases assign <id> --user <email> |
Assign a case (email, or raw user ID) |
cx cases unassign <id> |
Remove the assignee |
cx cases acknowledge <id> |
Acknowledge (signals you're working it; stops re-notification) |
cx cases unacknowledge <id> |
Remove the acknowledgment |
cx cases resolve <id> --reason <text> |
Resolve a case (irreversible — see below) |
cx cases close <id> |
Close a case (terminal) |
cx cases set-priority <id> --priority <P1..P5> |
Override the computed priority |
cx cases clear-priority <id> |
Remove a priority override |
cx cases events list <case-id> |
Event timeline (status changes, comments, assignments) |
cx cases events get <event-id> |
A single event — drill in, e.g. to expand a comment thread |
cx cases notifications <case-id> [<case-id> ...] |
Notification deliveries (connector, status, time) |
Case Lifecycle
PENDING_ACTIVATION ──► ACTIVE ◄────────► ACKNOWLEDGED
│ ╲ │ ╲
│ ╲ │ ╲
▼ ╲ ▼ ╲
CLOSED ╲──► RESOLVED ◄─── (from ACK)
│
▼
CLOSED (terminal)
| From state | Allowed transitions | Notes |
|---|---|---|
PENDING_ACTIVATION |
→ ACTIVE |
System-driven activation; not user-controllable |
ACTIVE |
→ ACKNOWLEDGED, RESOLVED, CLOSED |
Ack is optional; for a false alarm, close directly (skip resolve) |
ACKNOWLEDGED |
→ ACTIVE, RESOLVED, CLOSED |
The only "back" transition: unacknowledge returns it to ACTIVE |
RESOLVED |
→ CLOSED only |
Irreversible — cannot reopen to ACTIVE/ACKNOWLEDGED |
CLOSED |
(none) | Terminal |
What ships with it
2 files 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.
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.
- 5d ago First seen · 121 lines · 46 tokens per session scan A 66cc778bd61e
cx-cases is a skill published in the GitHub repository coralogix/cx-cli (116 stars, last pushed yesterday), licensed Apache-2.0. It adds 46 tokens to every session and 1,546 once invoked, about $0.0002 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…