healthcheck

healthcheck is a skill for Claude Code, Codex from spinabot/brigade. It costs 64 tokens per session (2,339 once invoked), scanned A, a copy of healthcheck, MIT.

A guide for checking and hardening the computer that runs Brigade, a deployment tool. It helps review firewall, SSH access, updates, exposure, backups, and security risk settings.

In plain words
What is it for?
Use it to audit a Brigade machine such as a laptop, server, VPS, or Raspberry Pi; review security exposure; plan firewall, SSH, and update hardening; and schedule recurring checks.
Why use it?
It brings host-security checks into one careful process while keeping the user's chosen risk level and access method in mind. It also requires approval before making changes.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions AGENTS.md.

Good fit Use it to audit a Brigade machine such as a laptop, server, VPS, or Raspberry Pi; review security exposure; plan firewall, SSH, and update hardening; and schedule recurring checks.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/spinabot/brigade/healthcheck
About the project

Brigade is an ecosystem for running crews of AI agents as a personal intelligence system, with local handling of credentials and support for exposing agent crews to the internet for testing. It is for people who want to organize and operate multiple AI agents using their own API keys or existing Claude, ChatGPT, Copilot, Claude Code, or Codex access. The catalogue skills provide workflows for using Brigade and its agent ecosystem.

spinabot/brigade · 3,498 stars · on GitHub · brigade.spinabot.com

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 spinabot/brigade --skill healthcheck
Clone the repo
git clone --depth 1 https://github.com/spinabot/brigade

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.

agentmods badge for healthcheck

README.md
[![agentmods](https://agentmods.dev/badge/skills/spinabot/brigade/healthcheck.svg)](https://agentmods.dev/skills/spinabot/brigade/healthcheck)
Your own site
<a href="https://agentmods.dev/skills/spinabot/brigade/healthcheck"><img src="https://agentmods.dev/badge/skills/spinabot/brigade/healthcheck.svg" alt="Measured on agentmods" height="20"></a>
Per session 64 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,339 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.
Origin 89% copy Near-identical to another mod 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.

ModelPer sessionOnce 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

Measured 8d ago against content hash 02b21d19e587, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

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 8d 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

This is a copy

89% identical to healthcheck — 72 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/healthcheck/SKILL.md · 246 lines

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.

Brigade Host Hardening

Overview

Assess and harden the host running Brigade, then align it to a user-defined risk tolerance without breaking access. Use Brigade 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 Brigade 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):

  1. OS and version (Linux/macOS/Windows), container vs host.
  2. Privilege level (root/admin vs user).
  3. Access path (local console, SSH, RDP, tailnet).
  4. Network exposure (public IP, reverse proxy, tunnel).
  5. Brigade gateway status and bind address.
  6. Backup system and status (e.g., Time Machine, system images, snapshots).
  7. Deployment context (local mac app, headless gateway host, remote gateway, container/CI).
  8. Disk encryption status (FileVault/LUKS/BitLocker).
  9. OS automatic security updates status. Note: these are not blocking items, but are highly recommended, especially if Brigade can access sensitive data.
  10. Usage mode for a personal assistant with full access (local workstation vs headless/remote vs other).

Read the full file on GitHub · 246 lines

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.

  1. 8d ago First seen · 246 lines · 64 tokens per session scan A 02b21d19e587

Subscribe to this mod's changes

healthcheck is a skill published in the GitHub repository spinabot/brigade (3,498 stars, last pushed 2d ago), 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. It is 89% identical to healthcheck, differing in 72 lines, and is treated as a copy.