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-slosgit 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-slos)<a href="https://agentmods.dev/skills/coralogix/cx-cli/cx-slos"><img src="https://agentmods.dev/badge/skills/coralogix/cx-cli/cx-slos.svg" alt="Measured on agentmods" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector pass
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.00108 | $0.01136 |
| Opus 5 | $0.00054 | $0.00568 |
| Sonnet 5 | $0.00022 | $0.00227 |
| Haiku 4.5 | $0.00011 | $0.00114 |
Grade A, and why
cx-slos 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 8d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SLO Management Skill
An SLO (Service Level Objective) defines a reliability target for a service — e.g. "99.9% of requests succeed over 28 days". Use this skill to inspect SLO definitions, judge whether they are healthy, and manage their lifecycle.
CLI Commands
| Command | Purpose |
|---|---|
cx slos list |
List all SLO definitions |
cx slos get <id> |
Get a single SLO by ID |
cx slos create --from-file <path> |
Create an SLO from a JSON definition [requires --yes] |
cx slos update --from-file <path> |
Replace an SLO definition from JSON [requires --yes] |
cx slos delete <id> |
Delete an SLO [requires --yes] |
- All commands support
-o jsonfor structured output and-p <profile>(repeatable) for multi-profile fan-out. create/updateread from--from-file <path>, or-for stdin (the default).create,update, anddeleteare write operations and require--yesin non-interactive / agent mode.
SLO Definition
The fields surfaced on every SLO:
| Field | Meaning |
|---|---|
name |
Human-readable SLO name |
description |
Optional description |
targetThresholdPercentage |
The objective, e.g. 99.9 |
sloType |
SLO_TYPE_REQUEST (request-based) or SLO_TYPE_WINDOW (window-based) |
sloTimeFrame |
Rolling window, e.g. SLO_TIME_FRAME_7_DAYS, SLO_TIME_FRAME_28_DAYS |
productType |
The pillar the SLO is computed from, e.g. SLO_PRODUCT_TYPE_APM |
Monitoring SLO Health
# All SLOs with their target and window
cx slos list -o json | jq '[.[] | {name, targetThresholdPercentage, sloType, sloTimeFrame}]'
# Inspect a single SLO in full
cx slos get <slo-id> -o json
Compare the live attainment against targetThresholdPercentage to judge whether
the SLO is healthy or burning error budget. A request-based SLO measures the
fraction of good events; a window-based SLO measures the fraction of good time
windows. After triage, pivot to the cx-telemetry-querying skill to find the root
cause of a breach in logs, spans, or metrics.
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.
- 8d ago First seen · 98 lines · 108 tokens per session scan A 226fd6a8647b
cx-slos is a skill published in the GitHub repository coralogix/cx-cli (116 stars, last pushed yesterday), licensed Apache-2.0. It adds 108 tokens to every session and 1,136 once invoked, about $0.0005 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…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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…