Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From okta-inspector
Reports Okta connector health: configuration state, token validity, and last-run freshness.
How this command is triggered — by the user, by Claude, or both
Slash command
/okta-inspector:statusFiles this command reads when invoked
The summary Claude sees in its command listing — used to decide when to auto-load this command
# /okta-inspector:status Non-destructive health check. Shows whether the connector is configured, whether the token still works, and when it last produced findings. ## How to run ## Output ## Status values - `ready` — all systems go - `not-configured` — setup not run - `token-missing` — token env var unset - `token-invalid` — Okta returned 401 on `/users/me` - `stale` — last run > 7 days
Non-destructive health check. Shows whether the connector is configured, whether the token still works, and when it last produced findings.
bash plugins/connectors/okta-inspector/scripts/status.sh
okta-inspector
status: ready
domain: acme.okta.com
org id: 00oab12c3d4E5f6G7h8
token source: $OKTA_API_TOKEN (valid)
caller: [email protected]
config: ~/.config/claude-grc/connectors/okta-inspector.yaml
last run: 5h ago (run_id 20260413-a1b2c3d4)
cached: 12 resources, 38 evaluations
ready — all systems gonot-configured — setup not runtoken-missing — token env var unsettoken-invalid — Okta returned 401 on /users/mestale — last run > 7 days11plugins reuse this command
First indexed Apr 17, 2026
Showing the 6 earliest of 11 plugins
npx claudepluginhub hzmonama/cli-grc-engineering --plugin okta-inspector/statusReports Okta connector health: configuration state, token validity, and last-run freshness.
/statusReports AWS Inspector connector health — checks configuration, credential validity, and last-run freshness. Produces status, account details, and cache stats.
/statusReports GitHub Inspector connector status: configuration state, auth validity, last-run freshness, cached findings, and GitHub rate limits.
/statusReports GCP Inspector connector health: configuration state, credential validity, and last-run freshness.
/pipeline-statusReports status of configured connectors: auth validity, last-run timestamps, cached resource/evaluation counts, stale signals, and aggregate health summary.
/security-postureReviews overall security posture by querying open findings by severity, agent/device coverage, and resolution trends over a configurable lookback period.