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.
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 spinabot/brigade --skill node-connectgit clone --depth 1 https://github.com/spinabot/brigadeWrote 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/spinabot/brigade/node-connect)<a href="https://agentmods.dev/skills/spinabot/brigade/node-connect"><img src="https://agentmods.dev/badge/skills/spinabot/brigade/node-connect/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/spinabot/brigade/node-connect"><img src="https://agentmods.dev/badge/skills/spinabot/brigade/node-connect.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.00079 | $0.01098 |
| Opus 5.5 | $0.00032 | $0.00439 |
| Sonnet 5.5 | $0.00016 | $0.00220 |
| Haiku 4.5 | $0.00008 | $0.00110 |
Grade A, and why
node-connect 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 1mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- node-connect — 88% identical, 44 lines differ
How it starts
The opening of the file, as written. The whole thing — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Node Connect
Goal: find the one real route from node -> gateway, verify Brigade is advertising that route, then fix pairing/auth.
Topology first
Decide which case you are in before proposing fixes:
- same machine / emulator / USB tunnel
- same LAN / local Wi-Fi
- same Tailscale tailnet
- public URL / reverse proxy
Do not mix them.
- Local Wi-Fi problem: do not switch to Tailscale unless remote access is actually needed.
- VPS / remote gateway problem: do not keep debugging
localhostor LAN IPs.
If ambiguous, ask first
If the setup is unclear or the failure report is vague, ask short clarifying questions before diagnosing.
Ask for:
- which route they intend: same machine, same LAN, Tailscale tailnet, or public URL
- whether they used QR/setup code or manual host/port
- the exact app text/status/error, quoted exactly if possible
- whether
brigade devices listshows a pending pairing request
Do not guess from can't connect.
Canonical checks
Prefer brigade qr --json. It uses the same setup-code payload Android scans.
brigade config get gateway.mode
brigade config get gateway.bind
brigade config get gateway.tailscale.mode
brigade config get gateway.remote.url
brigade config get gateway.auth.mode
brigade config get gateway.auth.allowTailscale
brigade config get plugins.entries.device-pair.config.publicUrl
brigade qr --json
brigade devices list
brigade nodes status
If this Brigade instance is pointed at a remote gateway, also run:
brigade qr --remote --json
If Tailscale is part of the story:
tailscale status --json
Read the result, not guesses
brigade qr --json success means:
gatewayUrl: this is the actual endpoint the app should use.urlSource: this tells you which config path won.
Common good sources:
gateway.bind=lan: same Wi-Fi / LAN onlygateway.bind=tailnet: direct tailnet accessgateway.tailscale.mode=serveorgateway.tailscale.mode=funnel: Tailscale routeplugins.entries.device-pair.config.publicUrl: explicit public/reverse-proxy routegateway.remote.url: remote gateway route
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.
- 1mo ago First seen · 143 lines · 79 tokens per session scan A 31719e08be55
node-connect is a skill published in the GitHub repository spinabot/brigade (11,352 stars, last pushed 6d ago), licensed MIT. It adds 79 tokens to every session and 1,098 once invoked, about $0.0003 per session on Opus 5.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
node-connect
Diagnose OpenClaw node connection and pairing failures for Android, iOS, and macOS companion apps. Use when QR/setup code/manual connect fails, local Wi-Fi works but VPS/tailnet does not, or errors mention pairing required, unauthorized, bootstrap token invalid or expired, gateway.bind, gateway.remote.url, Tailscale…
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
node-connect
Diagnose OpenClaw Control UI browser and native Android, iOS, or macOS node connection failures across route, auth, pairing, QR/setup-code, and reconnect states.
agent-merge-conflict-arbiter
Neutral arbiter for merge conflicts between two agents.
python-debugpy
Debug Python: pdb REPL + debugpy remote (DAP).
browser-edge-cases
SOP for debugging browser automation failures on complex websites. Use when browser tools fail on specific sites like LinkedIn, Twitter/X, SPAs, or sites with Shadow DOM.