scope-and-security

Enforce file access and action boundaries for AI agent workflows.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/j-mckerracher/agent-research --skill scope-and-security
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scope-and-security
Source: https://github.com/j-mckerracher/agent-research/tree/main/dated-agents/4-6-2026/.claude/skills/scope-and-security
Command: npx skills add https://github.com/j-mckerracher/agent-research --skill scope-and-security

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Defines clear boundaries for file access and action permissions in AI agent workflows, helping teams prevent accidental or intentional scope violations and secret exposure.

Core Features & Use Cases

  • Artifact root and code repository scoping: Enforces separate artifact roots for workflow artifacts while restricting code modifications to designated agents.
  • Forbidden file patterns: Prohibits modifying sensitive files such as .env, secrets, credentials, passwords, and common build artifacts like node_modules/, dist/, build/, as well as .git directories and lock files.
  • Forbidden actions: Blocks HTTP requests to external URLs, direct credential access, installation of global packages, and system configuration changes.
  • Secrets handling: Ensures secrets are never logged or echoed; references to secrets are made by name only and escalated if necessary.
  • Scope creep prevention: Detects out-of-scope requests, stops changes, and documents the need for scope expansion.

Quick Start

Apply scope-and-security rules to an agent task by verifying artifact scope, forbidden patterns, and prohibited actions before making changes.

Frequently Asked Questions about scope-and-security

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

FAQPage Schema
How do I prevent AI agents from modifying sensitive files like .env or secrets in my repository?

Scope-and-security prevents scope creep by detecting out-of-scope requests, stopping unauthorized changes, and documenting the need for scope expansion to keep agent workflows within approved boundaries.

Can I block AI agents from making external HTTP requests or installing global packages?

Scope-and-security handles secrets by ensuring they are never logged or echoed, allowing references by name only and escalating access requests if necessary to prevent credential exposure.

What is the best way to enforce artifact root boundaries for automated agent tasks?

Scope-and-security requires no external dependencies, aligning with automated scope validation via a dedicated script to verify compliance against defined rules before making changes.

How do I validate that an AI agent workflow complies with security rules before execution?

Scope-and-security prevents scope creep by detecting out-of-scope requests, stopping unauthorized changes, and documenting the need for scope expansion to keep agent workflows within approved boundaries.