guardrail-packs

Define and implement security guardrails and capability boundaries in AI harnesses.

Updated May 11, 2026
One-click install
npx skills add https://github.com/AesopScott/mojo --skill guardrail-packs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: guardrail-packs
Source: https://github.com/AesopScott/mojo/tree/main/harnesses/skills/guardrail-packs
Command: npx skills add https://github.com/AesopScott/mojo --skill guardrail-packs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the risk of uncontrolled capability expansion by providing a structured framework to define, test, and implement security boundaries for AI-driven workflows.

Core Features & Use Cases

  • Capability Control: Author secret patterns, approval-gate definitions, and credential-boundary policies as installable packs.
  • Risk Mitigation: Ensures that changes to system behavior are bounded, tested, and verified before affecting production environments.
  • Use Case: When a team needs to introduce a new automated action, they use this skill to define the specific permission boundary, ensuring the action cannot access sensitive secrets or exceed authorized spending limits.

Quick Start

Use the guardrail-packs skill to inspect the current capability boundary and propose a new rule pack for the target harness.

Frequently Asked Questions about guardrail-packs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I define security guardrails to prevent unauthorized system access in automated workflows?

Define security guardrails by authoring custom rule packs that specify secret patterns, approval gates, and credential boundaries to prevent unauthorized system access. These packs are installed in the harness to enforce capability boundaries.

What are capability boundaries in AI harnesses and when do I need them?

Capability boundaries in AI harnesses are structured security limits that restrict automated actions from accessing sensitive secrets or exceeding authorized spending limits. You need them when introducing new automated actions to prevent uncontrolled capability expansion.

How do I create custom rule packs for credential policies and approval gates?

Create custom rule packs by authoring secret patterns, approval-gate definitions, and credential-boundary policies as installable configuration files. Inspect the current capability boundary first, then propose a new rule pack for the target harness.

Does this guardrail framework require testing before enforcing new security policies?

Yes, the guardrail framework requires verification of all configuration changes through positive and boundary testing. This ensures that changes to system behavior are bounded, tested, and verified before affecting production environments.

What's the best way to enforce compliance and governance policies for AI-driven workflows?

The best way to enforce compliance and governance policies is implementing structured security guardrails as installable packs. This approach bounds system behavior changes and verifies them through testing before production deployment.

Can I set spending limits and secret patterns as approval gates in a security policy?

Yes, you can set spending limits and secret patterns as approval gates within security policy rule packs. The framework supports authoring these credential-boundary policies to ensure automated actions cannot exceed authorized limits.