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 skills add coralogix/cx-cli --skill cx-ai-centergit 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-ai-center)<a href="https://agentmods.dev/skills/coralogix/cx-cli/cx-ai-center"><img src="https://agentmods.dev/badge/skills/coralogix/cx-cli/cx-ai-center/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/coralogix/cx-cli/cx-ai-center"><img src="https://agentmods.dev/badge/skills/coralogix/cx-cli/cx-ai-center.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk warn
- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 42 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.1 | $0.00089 | $0.02449 |
| Opus 5 | $0.00044 | $0.01224 |
| Sonnet 5 | $0.00018 | $0.00490 |
| Haiku 4.5 | $0.00009 | $0.00245 |
Grade A, and why
cx-ai-center 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 11d 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 — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Center Skill
This is the tool for anything about AI/GenAI applications — both questions about their behavior (prompts/responses, quality, hallucinations, guardrails, security, cost/tokens, errors, latency — everything AI apps expose through their GenAI spans/tags) and actions to manage them (applications, evaluations/policies, policy↔app links, model pricing). If a request touches an AI application or its GenAI telemetry, use this skill.
Coralogix AI Center observes, evaluates, and guards GenAI/LLM applications. This skill answers questions about AI apps from two sources:
- Configuration (this skill's
cx ai-centercommands): the AI application inventory, configured evaluations/policies, coverage, custom evaluations, and model pricing — none of which live in span telemetry. - Telemetry (GenAI spans): what users asked, how the model answered, cost, tokens,
latency, errors, tool calls, and eval/guardrail verdicts — queried with
cx spans '<DataPrime>'. See references/ai-center-queries.md for the full, runnable query library, span schema, and playbooks.
Match the source to the question: "which apps lack guardrails" → config
(cx ai-center applications list); "what are users asking my chatbot" → telemetry
(cx spans '…', reading the conversation from the GenAI spans). Some questions need both —
e.g. "is my chatbot's PII policy actually catching PII?" joins config (is the policy enabled)
with telemetry (the PII verdicts + the messages).
Destructive Operation Safety
All write operations (create, update, delete, add, remove, set)
require interactive confirmation. ai-center is a risky command, so writes are also
gated by allow_risky_commands in ~/.cx/config.toml. To skip the prompt in scripts, pass
--yes.
IMPORTANT: NEVER pass --yes without explicit user approval. Before executing any write:
- Describe the exact operation to the user (what will be created/modified/deleted/linked).
- Wait for the user to confirm.
- Only then execute with
--yes.
What ships with it
3 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.
- 11d ago First seen · 201 lines · 89 tokens per session scan A d4c38be1c36f
cx-ai-center is a skill published in the GitHub repository coralogix/cx-cli (117 stars, last pushed yesterday), licensed Apache-2.0. It adds 89 tokens to every session and 2,449 once invoked, about $0.0004 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
llm-app-patterns
Production-ready patterns for building LLM applications. Covers RAG pipelines, agent architectures, prompt IDEs, and LLMOps monitoring. Use when designing AI applications, implementing RAG, building agents, or setting up LLM observability.
prompt-optimization
Improve a prompt on the evaluations workbench through a measured loop. Score the baseline first, then duplicate the target column, form a hypothesis from failing rows, edit the copy's prompt draft, run, compare pass rate and cost, and repeat until the numbers hold. Use when the user asks to optimize or improve a…
enhance-prompt
Transforms vague UI ideas into polished, Stitch-optimized prompts. Enhances specificity, adds UI/UX keywords, injects design system context, and structures output for better generation results.
prompt-engineer
Writes, refactors, and evaluates prompts for LLMs — generating optimized prompt templates, structured output schemas, evaluation rubrics, and test suites. Use when designing prompts for new LLM applications, refactoring existing prompts for better accuracy or token efficiency, implementing chain-of-thought or few-shot…
seedance-vocab-en
This skill should be used when an English Seedance 2.0 prompt needs clearer production wording, less generic prose, or precise vocabulary for camera, lighting, motion, VFX, audio, and constraints. Route blocked prompts through seedance-filter for context and boundary review.
ideogram4
Prompting patterns for Ideogram 4 text-to-image — best-in-class in-image text rendering and exact color/layout control via structured JSON captions. Use when generating images that need legible on-image text (title cards, thumbnails, logos, signage, CTAs), precise brand colors, or controlled spatial layout. Triggers…