From gcp-inspector
Reports GCP Inspector connector health: configuration state, credential validity, and last-run freshness.
How this command is triggered — by the user, by Claude, or both
Slash command
/gcp-inspector:statusFiles this command reads when invoked
The summary Claude sees in its command listing — used to decide when to auto-load this command
# /gcp-inspector:status Non-destructive health check. Shows whether the connector is configured, whether credentials still work, and when it last produced findings. ## How to run ## Output ## Status values - `ready` — all systems go - `not-configured` — setup not run - `credentials-expired` — `gcloud auth list` shows no active account - `project-inaccessible` — caller can't describe the configured project - `stale` — last run > 7 days ago
Non-destructive health check. Shows whether the connector is configured, whether credentials still work, and when it last produced findings.
bash plugins/connectors/gcp-inspector/scripts/status.sh
gcp-inspector
status: ready
gcloud: 557.0.0
project: acme-prod (1234567890)
caller: [email protected]
default region: us-central1
config: ~/.config/claude-grc/connectors/gcp-inspector.yaml
last run: 4h ago (run_id 20260413-a1b2c3d4)
cached: 18 resources, 64 evaluations
ready — all systems gonot-configured — setup not runcredentials-expired — gcloud auth list shows no active accountproject-inaccessible — caller can't describe the configured projectstale — last run > 7 days ago11plugins reuse this command
First indexed Apr 17, 2026
Showing the 6 earliest of 11 plugins
npx claudepluginhub hzmonama/cli-grc-engineering --plugin gcp-inspector/statusReports GCP Inspector connector health: configuration state, credential validity, and last-run freshness.
/statusReports GitHub Inspector connector status: configuration state, auth validity, last-run freshness, cached findings, and GitHub rate limits.
/statusReports AWS Inspector connector health — checks configuration, credential validity, and last-run freshness. Produces status, account details, and cache stats.
/pipeline-statusReports status of configured connectors: auth validity, last-run timestamps, cached resource/evaluation counts, stale signals, and aggregate health summary.
/statusReports Okta connector health: configuration state, token validity, and last-run freshness.
/harness-statusDisplays the current health of the project's harness — enforcement ratio, drift, and garbage collection state by reading HARNESS.md.