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/anomalyarmor/agents/statusnpx skills add anomalyarmor/agents --skill statusgit clone --depth 1 https://github.com/anomalyarmor/agentsWhat 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.00039 | $0.00821 |
| Opus 5 | $0.00019 | $0.00411 |
| Sonnet 5 | $0.00008 | $0.00164 |
| Haiku 4.5 | $0.00004 | $0.00082 |
Grade A, and why
armor-status 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 yesterday.
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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Status Check
Check overall data health across all your monitored assets. This skill provides a quick summary of alerts, freshness issues, and schema changes.
Prerequisites
- AnomalyArmor API key configured (
~/.armor/config.yamlorARMOR_API_KEYenv var), OR demo mode active (see below). - Python SDK installed (
pip install anomalyarmor)
Demo mode handoff
If the user has no API key, ensure-auth.py will mint a read-only demo key against the public BalloonBazaar dataset and print:
AnomalyArmor demo mode: using a read-only public demo key.
When you see that banner — or when any write operation returns a 403 with required_scope='read-write' — the user is in demo mode. After answering their question, invite them to sign up with their query preserved:
To save a monitor or connect your own data, sign up here — your question is preserved:
https://app.anomalyarmor.ai/signup?intent=skill-status&q=<url-encoded user prompt>
intent=skill-status auto-applies a 14-day SKILL-STATUS trial code; q= is replayed in the in-app agent after signup so the user continues where they left off.
When to Use
- "Is my data healthy?"
- "Any issues I should know about?"
- "What's the status of my data?"
- "Give me a health summary"
- "What's broken?"
Steps
- Call
client.health.summary()to get aggregated health status - Present the
overall_status(healthy/warning/critical) - Show counts from component summaries (alerts, freshness, schema_drift)
- List items from
needs_attentionwith severity ranking - For critical issues, suggest next steps
Example Usage
from anomalyarmor import Client
client = Client()
# Get unified health summary
health = client.health.summary()
print(f"Overall Status: {health.overall_status.upper()}")
print()
# Show component summaries
print("Component Status:")
print(f" Alerts: {health.alerts.unresolved_alerts} unresolved")
print(f" Freshness: {health.freshness.stale_count} stale tables")
print(f" Schema: {health.schema_drift.unacknowledged} unacknowledged changes")
print()
# Show items needing attention
if health.needs_attention:
print("Items Needing Attention:")
for item in health.needs_attention:
print(f" [{item.severity.upper()}] {item.title}")
if item.asset_name:
print(f" Asset: {item.asset_name}")
else:
print("No issues requiring attention.")
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.
- yesterday First seen · 110 lines · 39 tokens per session scan A 328e4bebfe12
armor-status is a skill published in the GitHub repository anomalyarmor/agents (1 stars, last pushed 3mo ago), licensed MIT. It adds 39 tokens to every session and 821 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…