smoke-test

smoke-test is a skill for Claude Code, Codex from cynthiajones34/GBrain. It costs 52 tokens per session (1,420 once invoked), scanned A, a copy of smoke-test, MIT.

A post-restart health check for gbrain and OpenClaw, with automatic fixes for known problems.

In plain words
What is it for?
Use it from the command line, startup scripts, or an agent to check runtimes, databases, workers, gateways, keys, and the brain repository.
Why use it?
It quickly shows whether essential services are working after a container restart and records any failures that remain.

Skill for Claude CodeCodex

Which agent this was written for is unclear — built for gbrain. Also seen: mentions Codex; built for gbrain.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is bash scripts/smoke-test.sh.

Good fit Use it from the command line, startup scripts, or an agent to check runtimes, databases, workers, gateways, keys, and the brain repository.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/cynthiajones34/GBrain
agentmods
npx agentmods add skills/cynthiajones34/gbrain/smoke-test

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 smoke-test

README.md
[![agentmods](https://agentmods.dev/badge/skills/cynthiajones34/gbrain/smoke-test/github.svg)](https://agentmods.dev/skills/cynthiajones34/gbrain/smoke-test)
Your own site
<a href="https://agentmods.dev/skills/cynthiajones34/gbrain/smoke-test"><img src="https://agentmods.dev/badge/skills/cynthiajones34/gbrain/smoke-test/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.

agentmods 80×15 button for smoke-test

Your own site · 80×15
<a href="https://agentmods.dev/skills/cynthiajones34/gbrain/smoke-test"><img src="https://agentmods.dev/badge/skills/cynthiajones34/gbrain/smoke-test.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 52 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,420 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 100% 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.00052 $0.01420
Opus 5 $0.00026 $0.00710
Sonnet 5 $0.00010 $0.00284
Haiku 4.5 $0.00005 $0.00142

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

Security

Grade A, and why

smoke-test 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 9d 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

100% identical to smoke-test — 0 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/smoke-test/SKILL.md · 161 lines

How it starts

The opening of the file, as written. The whole thing — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Smoke Test Skillpack

Run gbrain smoke-test or bash scripts/smoke-test.sh after any container restart.

Contract

This skill guarantees:

  • 8 core tests verify gbrain + OpenClaw health after restart
  • Known failures are auto-fixed before reporting
  • User-extensible via ~/.gbrain/smoke-tests.d/*.sh drop-in scripts
  • Results logged to /tmp/gbrain-smoke-test.log
  • Exit code = number of unfixed failures (0 = all pass)

Built-in Tests

# Test Auto-Fix
1 Bun runtime Install from bun.sh
2 GBrain CLI loads Reinstall deps
3 GBrain database (doctor)
4 GBrain worker process Start worker
5 OpenClaw Codex plugin (Zod CJS) npm install zod@4 --force
6 OpenClaw gateway — (may not be started yet)
7 Embedding API key — (check .env)
8 Brain repo exists

Usage

CLI

gbrain smoke-test

Direct

bash scripts/smoke-test.sh

From OpenClaw bootstrap

Add to your ensure-services.sh or equivalent:

bash /path/to/gbrain/scripts/smoke-test.sh >> /tmp/bootstrap.log 2>&1

From an agent

exec: bash /data/gbrain/scripts/smoke-test.sh

Adding Custom Tests

Create executable scripts in ~/.gbrain/smoke-tests.d/:

# ~/.gbrain/smoke-tests.d/check-redis.sh
#!/bin/bash
redis-cli ping | grep -q PONG

Rules:

  • Exit 0 = pass, non-zero = fail
  • Filename becomes the test name (e.g. check-redis from check-redis.sh)
  • Keep tests fast (< 10s each)
  • Tests run in alphabetical order

Adding Built-in Tests

Edit scripts/smoke-test.sh. Follow this pattern:

# ── N. [Service Name] ──────────────────────────────────────
if [test condition]; then
  pass "[Service Name]"
else
  # Auto-fix attempt
  [fix command]
  if [re-test condition]; then
    fixed "[What was fixed]"
    pass "[Service Name] (after fix)"
  else
    fail "[Service Name] — [error detail]"
  fi
fi

Design rules:

  1. Test first — never fix without confirming broken
  2. Re-test after fix — verify the fix worked
  3. Timeout everythingtimeout N on any command that could hang
  4. Use helperspass(), fail(), fixed(), skip()
  5. Idempotent fixes — safe to run repeatedly
  6. Skip gracefullyskip() when a prerequisite is missing, don't fail

Read the full file on GitHub · 161 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. 9d ago First seen · 161 lines · 52 tokens per session scan A f2f2172d41e6

Subscribe to this mod's changes

smoke-test is a skill published in the GitHub repository cynthiajones34/GBrain (0 stars, last pushed 1mo ago), licensed MIT. It adds 52 tokens to every session and 1,420 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to smoke-test, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

potpie-debug-memory

Use while debugging or troubleshooting failures, flaky tests, incidents, production alerts, CI failures, local dev setup issues, repeated bugs, prior fixes, failed attempts, and verification history.

potpie-ai/potpie · 41 tokens

potpie-project-preferences

Use before writing, modifying, reviewing, refactoring, or testing code so repo/project preferences surface: error handling, file structure, frameworks, logging, dependency choices, testing, security, API style, and naming. Also use after code work when a reusable project preference should be recorded.

potpie-ai/potpie · 63 tokens

closed-loop

Run one task through the V-model verification loop: CP-2 plan → CP-3 build → CP-3v component verify → CP-4 integration verify (full lane) → CP-5 acceptance. The worker never grades its own homework; evidence rows trace back to AC-n. Opt-in: invoke with /closed-loop or by asking for the closed loop, proper…

huytieu/COG-second-brain · 92 tokens

memory-proactive

Proactive layered recall and generic domain-aware routing.

mage0535/hermes-memory-installer · 14 tokens

dogfood

This skill guides you through systematic exploratory QA testing of web applications using the browser toolset. You will navigate the application, interact with elements, capture evidence of issues, and produce a structured bug report.

AtlasOmnia/donna-starter · 20 tokens

memory-archivist

A set of scripts for archiving conversations, syncing them to a knowledge graph, updating summaries, and managing stored memories over time. A knowledge graph is a linked collection of information and relationships.

mage0535/hermes-memory-installer · 22 tokens