Borrowing it
Nothing to install: this file belongs to 0xSoftBoi/suwappubot. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/0xSoftBoi/suwappubot/main/.claude/commands/status.mdgit clone --depth 1 https://github.com/0xSoftBoi/suwappubotWrote 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/commands/0xsoftboi/suwappubot/status)<a href="https://agentmods.dev/commands/0xsoftboi/suwappubot/status"><img src="https://agentmods.dev/badge/commands/0xsoftboi/suwappubot/status.svg" alt="Measured on agentmods" 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.00029 | $0.01082 |
| Opus 5 | $0.00015 | $0.00541 |
| Sonnet 5 | $0.00006 | $0.00216 |
| Haiku 4.5 | $0.00003 | $0.00108 |
Grade A, and why
status 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.
How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Suwappu Status Skill
One command to answer "is anything broken right now?" across all Railway services. Run this before diagnosing anything and after every deploy.
python3 scripts/status.py # full check (prod)
python3 scripts/status.py --quick # skip log scan — fast
python3 scripts/status.py --env dev
python3 scripts/status.py --json # machine-readable (cron/CI)
python3 scripts/status.py --logs api-ts --lines 300 # dump one service's logs
Exit codes: 0 healthy, 1 degraded/down, 2 could not determine.
Why this exists (read before reaching for another tool)
We have three overlapping health tools and they check different layers. Using the wrong one is how outages get missed:
| Tool | Layer | Blind spot |
|---|---|---|
.github/workflows/health-check.yml |
public HTTP, every 10 min | only services with a public URL |
scripts/monitor.sh |
public HTTP + log classification | same — no control plane |
scripts/health-triage.sh |
one endpoint + Claude root-cause | single service |
scripts/status.py |
Railway control plane + HTTP + logs + CI | needs railway CLI auth |
The blind spot that matters: python-worker, suwappu-relayer and
suwappu-bridge have no public health URL. They can crash-loop or fail to deploy
and every HTTP probe still returns 200. Only status.py sees this, because it
reads Railway's deployment state directly rather than inferring it from traffic.
The inverse failure is just as real: a deploy can fail while the old container
keeps serving happily, so health stays green while your new code is not live.
status.py shows deploy status and age, which makes that obvious.
How it works
- Service list is derived from Railway at runtime (
railway status --json), not hardcoded — new services are covered automatically instead of drifting out of a stale list. - Probes run in parallel; log scanning only happens for services that already look unhealthy, so the common all-green path stays fast.
- For
python-apiit parses the deep/healthpayload and prints only the subsystems that are not healthy (db, redis, background-service heartbeats).
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.
- 8d ago First seen · 83 lines · 29 tokens per session scan A 9b4605400434
status is a command published in the GitHub repository 0xSoftBoi/suwappubot (3 stars, last pushed yesterday), licensed Apache-2.0. It adds 29 tokens to every session and 1,082 once invoked, about $0.0001 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 commands, from other repositories
debug-order
Debug why a CoW Protocol order failed to match.
krait
Run a complete multi-phase security audit on the target codebase.
krait-fuzz
Run an invariant-based fuzzing campaign: Understand → Extract Invariants → Generate Foundry Tests → Run & Fix Iteratively → Report.
krait-poc
Write and run a valid Foundry proof-of-concept that proves (or disproves) a Solidity exploit by asserting the actual harm on a forked chain or against local source.
krait-init
Standalone readiness check before running /krait. Verifies tools, project shape, gitignore, MCP wiring, and /.claude install. Reports what's missing — does NOT install or modify anything.
dashboard
Open the ChainGPT marketplace dashboard (localhost web UI — Overview, Skills, Activity, Health, About).