Deploy your own Open-Inspect instance. Use when the user wants to set up, deploy, or onboard to Open-Inspect. Guides through repository setup, credential collection, Terraform deployment, and verification with user handoffs.
70
86%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
High
Do not use without reviewing
Security
1 high severity finding. You should review these findings carefully before considering using this skill.
The skill handles credentials insecurely by requiring the agent to include secret values verbatim in its generated output. This exposes credentials in the agent’s context and conversation history, creating a risk of data exfiltration.
The skill explicitly instructs collecting secrets and embedding them verbatim into commands and tfvars (e.g., CLI args, cat-ing private keys, writing access_key/secret_key), which requires the LLM/agent to handle and output secret values directly, creating a high exfiltration risk.
Low
Low-risk findings.
1 low severity finding. Worth noting, but not necessarily harmful.
The skill fetches instructions or code from an external URL at runtime, and the fetched content directly controls the agent’s prompts or executes code. This dynamic dependency allows the external source to modify the agent’s behavior without any changes to the skill itself.
The guide instructs cloning a remote repository at git@github.com:ColeMurray/open-inspect.git during runtime (SKILL.md:54-54), which fetches external code that is then built/executed (npm install/npm run build), so this remote repo is a runtime dependency that can execute arbitrary code.
f3cd32d
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.