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 CloudChef/atlasclaw-providers --skill alarmgit clone --depth 1 https://github.com/CloudChef/atlasclaw-providersWrote 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/cloudchef/atlasclaw-providers/alarm)<a href="https://agentmods.dev/skills/cloudchef/atlasclaw-providers/alarm"><img src="https://agentmods.dev/badge/skills/cloudchef/atlasclaw-providers/alarm/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/cloudchef/atlasclaw-providers/alarm"><img src="https://agentmods.dev/badge/skills/cloudchef/atlasclaw-providers/alarm.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00032 | $0.03245 |
| Opus 5 | $0.00016 | $0.01622 |
| Sonnet 5 | $0.00006 | $0.00649 |
| Haiku 4.5 | $0.00003 | $0.00325 |
Grade A, and why
alarm 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 9d 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 — 317 lines — stays where its author put it; the contents beside it link to each section on GitHub.
alarm
Alarm and resource-health workflow for triggered alert retrieval, rule-aware alert analysis, component-model-driven resource health evidence, and status operations.
Purpose
Provide alarm-management capabilities:
- List triggered alerts with machine-readable metadata
- Resolve one exact resource and distinguish current firing/muted alerts from currently resolved alerts triggered within the configured lookback for comprehensive resource analysis
- Analyze one alert with normalized facts, datasource-enriched resource context, assessment, and remediation guidance
- Analyze one resource independently of alerts by handing component-specific monitoring evidence to the LLM
- Perform validated status operations (
mute,resolve,reopen)
Handlers and helpers
scripts/adapter.py contains the four Tool handlers: list_alerts,
analyze_alert, analyze_resource_health, and operate_alert. It converts
AtlasClaw Context and Tool parameters, then calls SmartCMP Provider.
scripts/_alarm_object_actions.py remains separate because the embedded
assistant Context resolver calls it to build alert page actions. It is not a
one-command forwarding script.
Workflow
See references/WORKFLOW.md for the supported workflow.
Resource Enrichment
During alert analysis, the Adapter uses SmartCMP Provider resource
resolution when the alert exposes entityInstanceId or nodeInstanceId.
- Resolve related SmartCMP resources before finalizing the analysis narrative.
- Merge normalized
type + propertiesresource facts into the alert analysis payload. - If resource lookup is unavailable, continue the alert analysis with alert and policy facts, and treat resource enrichment as best-effort context.
Resource Health Analysis
Resource health analysis is independent of alert analysis:
- Resolve the resource through datasource resource helpers and use its normalized
componentType. - Load the effective monitoring model for that component; never substitute a generic VM metric list.
- Query only PromQL that can be scoped to the resolved resource through model-declared labels and exporter identity.
- Emit descriptive statistics and monitoring coverage, but leave
healthy,abnormal, orindeterminatejudgment to the AtlasClaw LLM. - The final LLM response must include status, confidence, principal findings, metric evidence, missing evidence, and recommended actions.
- Treat disabled, unavailable, or missing monitoring as an evidence gap rather than proof that the resource is healthy or unhealthy.
- Do not read active alerts or alarm-policy thresholds for the resource-health conclusion.
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.
- 9d ago First seen · 317 lines · 32 tokens per session scan A 2663e145373a
alarm is a skill published in the GitHub repository CloudChef/atlasclaw-providers (15 stars, last pushed 5d ago), licensed Apache-2.0. It adds 32 tokens to every session and 3,245 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
use-agently
Discover (by searching) to use thousands of AI agents, MCP, tools, data sources, and APIs on the use-agently.com AI Agent Marketplace/Directory. You can get more effective "Web Search", "Web Fetch" or "Social Search" with use-agently. Sending messages via the A2A protocol, calling MCP tools, making HTTP/Web requests…
grizzly_sms
SMS verification and virtual phone numbers via Grizzly SMS API.
quality-assurance
A software quality and release-checking guide for reviewing code, testing applications, checking performance, and verifying delivery materials.
ci-cd-pipeline
A workflow for setting up CI/CD, meaning automated checks, builds, and deployments whenever code changes.
grizzly_sms
SMS verification and virtual phone numbers via Grizzly SMS API.
baoyu-image-gen
AI image generation with OpenAI, Google, DashScope and Replicate APIs. Supports text-to-image, reference images, aspect ratios. Sequential by default; parallel generation available on request. Use when user asks to generate, create, or draw images.