Security / Runtime Hardening

Environment Risk Assessment

Assess whether the runtime environment is safe for autonomous agent execution and recommend isolation or approval boundaries.

DocumentationAgent instructionsRequirements & limits

Use when you need to assess whether the current runtime is safe for autonomous agent execution.

Inputs

  • runtime description
  • mounted paths
  • credential sources
  • network and approval settings

Outputs

  • Environment risk review
  • Escalation reasons
  • Isolation recommendations

Before you begin

  • Reading and copying the procedure require no terminal setup. Check requirements for any packaged programs separately.

Try this first

Read the procedure and supply its documented inputs. Use the full text in an agent app or chat that supports pasted instructions, following that host's guidance.

Limits for this step
  • Instruction package only; it does not provide or authorize an executable runtime capability.
  • Safe for inspection and recommendation; require human approval before changing runtime isolation or credential policies.
Read full instructionsHide full instructionsSKILL.md · v0.1.0

Environment Risk Assessment

When to use

  • Use before enabling autonomous or semi-autonomous execution.
  • Use when an agent runs on a developer workstation.
  • Use when production credentials or broad mounts may be present.

Inputs required

  • runtime description
  • mounted paths
  • credential sources
  • network and approval settings

Workflow

  1. Identify whether the runtime is isolated or shared.
  2. Review credentials, mounts, and network scope.
  3. Flag unsafe mixes such as prod credentials on a laptop or broad writable mounts.
  4. Recommend safer boundaries and required approvals.

Output format

  • Environment Summary
  • High-Risk Conditions
  • Recommended Isolation Changes
  • Approval Recommendation

Guardrails

  • Default to conservative risk ratings when evidence is incomplete.
  • Prefer recommend-and-escalate over automated reconfiguration.
  • Cite the observed environment signals for each risk call.
  • Do not claim an environment is safe without explicit evidence.

Failure modes

  • If the runtime description is partial, mark confidence as low.
  • If protected paths are writable, require human review.
  • If production credentials are detected, escalate immediately.
View file metadata
---
name: environment-risk-assessment
description: Evaluate whether an agent runtime is isolated enough for the
  current task and flag unsafe mixes of credentials, mounts, and privileges.
---

Summary sources · Catalogue metadata, skill.yaml, SKILL.md, examples/input.json, examples/output.json · v0.1.0 · Release package

Install instruction files

These commands copy guidance into the selected runtime directories. Confirm that your agent app discovers it. Any packaged programs need separate setup and verification.

Install (Codex)

./bin/skills-hub install security/[email protected] --runtime codex

Install (Claude)

./bin/skills-hub install security/[email protected] --runtime claude

Install (Generic)

./bin/skills-hub install security/[email protected] --runtime generic --target ./my-agent/skills

How You Can Use This

Documentation

Resource form: Agent instructions

Read or copy the guidance. Any packaged programs have separate execution requirements and evidence.

First run: Read SKILL.md and follow the documented workflow.

Current limits

  • Instruction package only; it does not provide or authorize an executable runtime capability.
What installation and verification mean
File installation
Places package files and generated configuration in the selected directories.
Native discovery
Your agent app finds and accepts the instructions, tools or plugin registrations.
Mock execution
Exercises sample fixtures. Connected data and provider effects need a separate check.
Connected operation
Requires current configuration, provider authentication, scoped permissions and a successful operation in your intended environment.

Declared compatibility

Compatibility unknown: versions and capabilities have not been declared.

Classification: declared

Technical details and release files

Operational Summary

Execution mode: read-only-local-inspection

Approval boundary: Safe for inspection and recommendation; require human approval before changing runtime isolation or credential policies.

Review and lifecycle

Review maturity: Experimental

Security review declaration: Not declared

Lifecycle: Active

These release declarations are separate from evidence that a workflow operates in your environment.

Runtime & Dependencies

ID: security/environment-risk-assessment

Tags: runtime, isolation, environment, risk

Runtimes: codex, claude, generic

Tool dependencies: 0

API dependencies: 0

Dependencies

Tools: Not documented

APIs: Not documented

Outputs

  • Environment risk review
  • Escalation reasons
  • Isolation recommendations