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 orcasecurity/orca-skills --skill orca-account-healthgit clone --depth 1 https://github.com/orcasecurity/orca-skillsWrote 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/orcasecurity/orca-skills/orca-account-health)<a href="https://agentmods.dev/skills/orcasecurity/orca-skills/orca-account-health"><img src="https://agentmods.dev/badge/skills/orcasecurity/orca-skills/orca-account-health/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/orcasecurity/orca-skills/orca-account-health"><img src="https://agentmods.dev/badge/skills/orcasecurity/orca-skills/orca-account-health.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- 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.00094 | $0.03130 |
| Opus 5 | $0.00047 | $0.01565 |
| Sonnet 5 | $0.00019 | $0.00626 |
| Haiku 4.5 | $0.00009 | $0.00313 |
Grade A, and why
orca-account-health 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 12d 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 — 336 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orca Account Health Skill
Answers the question: "Is every account connected, recently synced, and fully scanned — so we can trust the data we're about to act on?"
Blind spots in account coverage produce blind spots in every other skill: if prod-eu-west last synced 48 hours ago, the alerts you triage are stale. This skill audits the foundation.
Usage
/orca-account-health
/orca-account-health aws
/orca-account-health degraded
Or natural language:
- "are all accounts connected?"
- "is everything synced?"
- "coverage audit before the audit"
- "any blind spots?"
- "show me account health"
Processing Logic
Step 1: Determine Scope
Parse the input:
- No arg: full inventory across all clouds.
- Provider arg (
aws,gcp,azure,kubernetes,oci): filter to one cloud. - Status arg (
degraded,offline,healthy): filter by health.
Step 2: Pull integration configs (single call)
get_integration_configs_data:
This returns every configured integration / source: cloud accounts, log sources (CloudTrail, Azure Monitor, etc.), Kubernetes clusters, and their extraction settings. Parse out:
- Source type and provider
- Connection state
- Last successful run / sync timestamp
- Any error messages or degraded indicators
Step 3: Cross-check coverage with discovery (parallel)
In parallel with Step 2, run two discovery_search queries to spot-check that data is actually flowing — not just that the connection exists:
Query A: Asset freshness per account
discovery_search:
search_phrase: "assets grouped by cloud account"
limit: 50
Query B: Recent CDR event flow (confirms log ingestion, not just inventory)
discovery_search:
search_phrase: "cloud audit events in the last 24 hours grouped by account"
limit: 50
If an account appears in get_integration_configs_data but returns zero assets or zero recent CDR events, that's a covert blind spot even though the integration reports "connected."
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.
- 12d ago First seen · 336 lines · 94 tokens per session scan A 150955fe4590
orca-account-health is a skill published in the GitHub repository orcasecurity/orca-skills (50 stars, last pushed 6d ago), licensed MIT. It adds 94 tokens to every session and 3,130 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
ml-pipeline-workflow
Build end-to-end MLOps pipelines from data preparation through model training, validation, and production deployment. Use when creating ML pipelines, implementing MLOps practices, or automating model training and deployment workflows.
netlify-deploy
Deploy web projects to Netlify using the Netlify CLI (npx netlify). Use when the user asks to deploy, host, publish, or link a site/repo on Netlify, including preview and production deploys.
game-pipeline
Game lifecycle orchestrator: scaffold, assets, audio, QA, deploy.
public-web-deploy
Publish a public website safely: DNS, web server, HTTPS, hardening, verify. Routes raw dev servers through nginx/Caddy/Apache/Cloudflare Pages.
service-health-check
Service health monitoring, endpoint validation, and CVE source auditing.
docker-devops
Docker/K8s: Dockerfile, multi-stage, compose, manifests, Helm. Triggers: Docker, Dockerfile, container, Kubernetes, k8s, compose, Helm, pod.