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 splunk-inspector
Configure `splunk-inspector` for a Splunk management API endpoint.
How this command is triggered — by the user, by Claude, or both
Slash command
/splunk-inspector:setupThe summary Claude sees in its command listing — used to decide when to auto-load this command
# /splunk-inspector:setup Configure `splunk-inspector` for a Splunk management API endpoint. The setup command validates `/services/server/info` and writes: Secrets are stored separately with user-only file permissions at: ## Auth Prefer Splunk bearer tokens. Basic auth is supported for local/admin workflows. Options: - `--base-url=<url>` Splunk management API base URL, usually port `8089`. - `--token=<token>` or `SPLUNK_TOKEN`. - `--username=<user> --password=<password>` or `SPLUNK_USERNAME` / `SPLUNK_PASSWORD`. - `--insecure` allows self-signed certificates by setting `NODE_T...
Configure splunk-inspector for a Splunk management API endpoint.
plugins/connectors/splunk-inspector/scripts/setup.sh --base-url=https://splunk.example.com:8089 --token=<token>
The setup command validates /services/server/info and writes:
~/.config/claude-grc/connectors/splunk-inspector.yaml
Secrets are stored separately with user-only file permissions at:
~/.config/claude-grc/connectors/splunk-inspector.env
Prefer Splunk bearer tokens. Basic auth is supported for local/admin workflows.
Options:
--base-url=<url> Splunk management API base URL, usually port 8089.--token=<token> or SPLUNK_TOKEN.--username=<user> --password=<password> or SPLUNK_USERNAME / SPLUNK_PASSWORD.--insecure allows self-signed certificates by setting NODE_TLS_REJECT_UNAUTHORIZED=0./splunk-inspector:collect
/splunk-inspector:status
/setupInitializes or resumes Conductor project setup by creating foundational documentation (product definition, tech stack, workflow, style guides) through interactive Q&A.
/setupChecks whether the local Codex CLI is ready and optionally toggles the stop-time review gate. If Codex is not installed, prompts the user to install it via npm.
/setupGuides enterprise admin through provisioning a cloud backend (Vertex/Bedrock/Foundry/gateway) for the Claude Office add-in, handles admin consent, and generates a deployable manifest.xml.
/setupDetects ghost installations of the claude-hud plugin by checking cache and registry state, and offers cleanup of orphaned files.
/setupInteractive setup wizard that detects installed AI providers, configures auth, and optimizes token usage for the Octopus ecosystem. Runs on first install or manual invocation.
6plugins reuse this command
First indexed Jul 18, 2026
npx claudepluginhub mrcodechef/claude-grc-engineering --plugin splunk-inspector