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 aleksbuss/orchestra --skill healthcheckgit clone --depth 1 https://github.com/aleksbuss/orchestraWrote 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/aleksbuss/orchestra/healthcheck)<a href="https://agentmods.dev/skills/aleksbuss/orchestra/healthcheck"><img src="https://agentmods.dev/badge/skills/aleksbuss/orchestra/healthcheck/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/aleksbuss/orchestra/healthcheck"><img src="https://agentmods.dev/badge/skills/aleksbuss/orchestra/healthcheck.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.00064 | $0.02339 |
| Opus 5 | $0.00032 | $0.01170 |
| Sonnet 5 | $0.00013 | $0.00468 |
| Haiku 4.5 | $0.00006 | $0.00234 |
Grade A, and why
healthcheck 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.
How it starts
The opening of the file, as written. The whole thing — 246 lines — stays where its author put it; the contents beside it link to each section on GitHub.
orchestra Host Hardening
Overview
Assess and harden the host running orchestra, then align it to a user-defined risk tolerance without breaking access. Use orchestra security tooling as a first-class signal, but treat OS hardening as a separate, explicit set of steps.
Core rules
- Recommend running this skill with a state-of-the-art model (e.g., Opus 4.5, GPT 5.2+). The agent should self-check the current model and suggest switching if below that level; do not block execution.
- Require explicit approval before any state-changing action.
- Do not modify remote access settings without confirming how the user connects.
- Prefer reversible, staged changes with a rollback plan.
- Never claim orchestra changes the host firewall, SSH, or OS updates; it does not.
- If role/identity is unknown, provide recommendations only.
- Formatting: every set of user choices must be numbered so the user can reply with a single digit.
- System-level backups are recommended; try to verify status.
Workflow (follow in order)
0) Model self-check (non-blocking)
Before starting, check the current model. If it is below state-of-the-art (e.g., Opus 4.5, GPT 5.2+), recommend switching. Do not block execution.
1) Establish context (read-only)
Try to infer 1–5 from the environment before asking. Prefer simple, non-technical questions if you need confirmation.
Determine (in order):
- OS and version (Linux/macOS/Windows), container vs host.
- Privilege level (root/admin vs user).
- Access path (local console, SSH, RDP, tailnet).
- Network exposure (public IP, reverse proxy, tunnel).
- orchestra gateway status and bind address.
- Backup system and status (e.g., Time Machine, system images, snapshots).
- Deployment context (local mac app, headless gateway host, remote gateway, container/CI).
- Disk encryption status (FileVault/LUKS/BitLocker).
- OS automatic security updates status. Note: these are not blocking items, but are highly recommended, especially if orchestra can access sensitive data.
- Usage mode for a personal assistant with full access (local workstation vs headless/remote vs other).
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 · 246 lines · 64 tokens per session scan A 39b22474ac79
healthcheck is a skill published in the GitHub repository aleksbuss/orchestra (2 stars, last pushed today), licensed MIT. It adds 64 tokens to every session and 2,339 once invoked, about $0.0003 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
data-analysis
A careful workflow for working with table-like files such as CSV, Excel, TSV, JSON, and Parquet. It requires inspecting the data before writing small analysis steps, then checking each result.
deep-research
Use this skill for any task that requires in-depth research, investigation, or comprehensive report generation on a topic. This includes: producing industry analysis, market research, technology surveys, competitive intelligence, trend reports, or any deliverable that synthesizes information from multiple sources into…
ama-memory
Use AMA memory in OpenClaw to recall prior context, capture turns, inspect stored state, end sessions, or delete a user's memory when asked.
cg-work-memory
Use when a local agent needs to submit a concise public work-memory report for its own completed local task through cg report work-memory.
comm-agent-skill
Communication specialist for the OpenClaw multi-agent system. Use this skill when the task involves: drafting or sending emails, posting to Discord or other chat platforms, scheduling calendar events, sending notifications, or any outbound communication on behalf of the user. Always drafts before sending and requires…
data-agent-skill
Data processing and analysis specialist for the OpenClaw multi-agent system. Use this skill when the task involves: parsing CSV/JSON/Excel files, data cleaning and transformation, SQL queries, statistical analysis, generating charts or visualizations, aggregating data from multiple sources, or extracting insights from…