ss-cli-agent-check
Agent Check — Secret Server Token Validation
Use this skill at the start of any workflow that requires Secret Server access. It validates the current token and surfaces the result so you can decide whether to proceed or prompt the user to re-authenticate.
When to use
- Before any
ss-cli get,ss-cli run,ss-cli refresh-env, or other secret access - In automated pipelines to fail fast before attempting secret operations
- When the user asks you to fetch or use a secret
How to check the token
Run the token status check and parse the JSON response:
ss-cli token-status --json
Response fields:
More from sieteunoseis/ss-cli
ss-cli-deploy
Deploys a Docker Compose service with secrets from Delinea Secret Server injected as environment variables. Secrets are never written to disk — they exist only in the subprocess memory. Use when deploying services that need credentials.
2ss-cli-env-sync
Syncs secrets from Delinea Secret Server to a .env file using a JSON map. Use when the user asks to refresh, update, or pull credentials into an env file. Requires a valid ss-cli token.
2ss-cli-rotate-and-sync
Updates a secret field in Delinea Secret Server and immediately re-syncs downstream env files. Use when the user asks to rotate a credential, change a password, or update a secret value.
2ss-cli-resolve-and-deploy
Resolves <ss:ID:field> placeholders in a config template using Delinea Secret Server secrets, then deploys the result to a remote server via SSH. Secrets flow through stdin/stdout only — never stored on disk. Use when deploying config files that contain credentials.
2ss-cli
Use when managing secrets from Delinea Secret Server — fetching credentials, syncing env files, deploying with injected secrets, resolving config templates, and rotating passwords. Covers all ss-cli operations.
1