What is axiom-alerting?

A tool for managing Axiom monitors and notifiers through Axiom's public API. A monitor detects conditions in data, while a notifier sends the resulting alert to a configured destination.

Use it to list, inspect, create, update, delete, and review the history of Axiom monitors and notifiers, and to validate alert configurations through the provided scripts.

It lets teams maintain both the rules that detect problems and the routes that deliver notifications in one workflow.

axiom-alerting — Skill for Claude Code and Codex by openclaw

About the project

ClawHub is a public registry where OpenClaw users publish, version, search, and install text-based agent skills and OpenClaw packages. It provides web browsing, a CLI-oriented API, moderation, vector search, and artifact hosting for code plugins, bundle plugins, and experimental whole-agent packages. The catalogue skills and agents are entries that can be discovered or used through this registry.

openclaw/clawhub · 9,407 stars · on GitHub · clawhub.ai

Install

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.

Any agent

npx skills add openclaw/clawhub --skill axiom-alerting

Clone the repo

git clone --depth 1 https://github.com/openclaw/clawhub

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/openclaw/clawhub/axiom-alerting/github.svg)](https://agentmods.dev/skills/openclaw/clawhub/axiom-alerting)

Your own site

<a href="https://agentmods.dev/skills/openclaw/clawhub/axiom-alerting"><img src="https://agentmods.dev/badge/skills/openclaw/clawhub/axiom-alerting/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/openclaw/clawhub/axiom-alerting"><img src="https://agentmods.dev/badge/skills/openclaw/clawhub/axiom-alerting.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,197 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector warn 7 Sept 2026

SkillSpector: 3 findings, 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 3
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.
medium Data Exfiltration · line 12
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.

Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
medium Data Exfiltration · line 221
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.

Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

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.00042	$0.02197
Opus 5	$0.00021	$0.01099
Sonnet 5	$0.00008	$0.00439
Haiku 4.5	$0.00004	$0.00220

Measured 10d ago against content hash 714cc41bd9fd, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

axiom-alerting 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 10d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

axiom-alerting — 100% identical, 0 lines differ

.agents/skills/axiom-alerting/SKILL.md · 292 lines

How it starts

The opening of the file, as written. The whole thing — 292 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Axiom Alerting

You manage alerting in Axiom end-to-end: notifiers for routing and monitors for detection.

API Overview

Base URL: https://api.axiom.co/v2/ with Bearer token auth from .axiom.toml (project root or ~/.axiom.toml).

Monitors (`/v2/monitors`)

Operation	Method	Path
List	GET	`/v2/monitors`
Get	GET	`/v2/monitors/{id}`
History	GET	`/v2/monitors/{id}/history`
Create	POST	`/v2/monitors`
Update	PUT	`/v2/monitors/{id}`
Delete	DELETE	`/v2/monitors/{id}`

Notifiers (`/v2/notifiers`)

Operation	Method	Path
List	GET	`/v2/notifiers`
Get	GET	`/v2/notifiers/{id}`
Create	POST	`/v2/notifiers`
Update	PUT	`/v2/notifiers/{id}`
Delete	DELETE	`/v2/notifiers/{id}`

Prerequisites

Run scripts/setup
Ensure .axiom.toml has a deployment:

[deployments.prod]
url = "https://api.axiom.co"
token = "xaat-your-token"
org_id = "your-org-id"

Scripts

Core:

scripts/axiom-api <deploy> <method> <path> [body]

Monitor scripts:

scripts/monitor-list <deployment> [--json]
scripts/monitor-get <deployment> <id>
scripts/monitor-history <deployment> <id> <startTime> <endTime>
scripts/monitor-create <deployment> <json-file>
scripts/monitor-update <deployment> <id> <json-file>
scripts/monitor-delete <deployment> <id>

Notifier scripts:

scripts/notifier-list <deployment> [--json]
scripts/notifier-get <deployment> <id>
scripts/notifier-create <deployment> <json-file>
scripts/notifier-update <deployment> <id> <json-file>
scripts/notifier-delete <deployment> <id>

Recommended Workflow

Create notifier first.
Create monitor and set notifierIds.
Validate monitor behavior with monitor-history.
Iterate monitor thresholds and schedule.

Workflow: End-To-End Alerting

Run scripts/setup.
List existing notifiers with scripts/notifier-list <deployment> and reuse one if appropriate.
If no suitable notifier exists, create one with scripts/notifier-create.
Create or update the monitor with notifierIds attached.
Validate with scripts/monitor-history <deployment> <id> <startTime> <endTime>.
If behavior is noisy or silent, tune threshold, rangeMinutes, intervalMinutes, and N-of-M trigger fields.
Re-check history after each change.

Read the full file on GitHub · 292 lines

Files

What ships with it

15 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.

Changes

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.

10d ago First seen · 292 lines · 42 tokens per session scan A 714cc41bd9fd

Subscribe to this mod's changes

axiom-alerting is a skill published in the GitHub repository openclaw/clawhub (9,407 stars, last pushed today), licensed MIT. It adds 42 tokens to every session and 2,197 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.

Analytics and metrics DevOps and cloud directory skill

axiom-alerting

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

Copies of this mod

How it starts

Axiom Alerting

API Overview

Monitors (`/v2/monitors`)

Notifiers (`/v2/notifiers`)

Prerequisites

Scripts

Recommended Workflow

Workflow: End-To-End Alerting

What ships with it

What this file has done since we first saw it

Other skills, from other repositories

directory-based-skill

dev-workflow

video-frames

happiness-skill

unity-dotween

unity-architecture

axiom-alerting

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

Copies of this mod

How it starts

Axiom Alerting

API Overview

Monitors (/v2/monitors)

Notifiers (/v2/notifiers)

Prerequisites

Scripts

Recommended Workflow

Workflow: End-To-End Alerting

What ships with it

What this file has done since we first saw it

Other skills, from other repositories

directory-based-skill

dev-workflow

video-frames

happiness-skill

unity-dotween

unity-architecture

Monitors (`/v2/monitors`)

Notifiers (`/v2/notifiers`)