harness-agent-permissions

Assigns role-based permission matrices to OpenCode and Cursor agents and subagents.

Updated Jul 29, 2026
One-click install
npx skills add https://github.com/MaiconGambini/opencode-harness-guide --skill harness-agent-permissions-maicongambini
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: harness-agent-permissions
Source: https://github.com/MaiconGambini/opencode-harness-guide/tree/main/skills/harness-agent-permissions
Command: npx skills add https://github.com/MaiconGambini/opencode-harness-guide --skill harness-agent-permissions-maicongambini

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When delegating work to AI agents and subagents in OpenCode or Cursor, unclear permissions can lead to agents editing files they should not touch or running unsafe commands. This Skill provides a default permission matrix that maps each agent role to explicit allow, deny, ask, or scoped rules. ## Core Features & Use Cases - Role-based permission matrix: Defines read, edit, bash, task, and external_directory permissions for Planner, Generator, Evaluator, and Security reviewer roles. - Safe defaults: Generators get scoped edit access, evaluators can run targeted checks, and external directory access is denied by default for all roles. - Workflow integration: Designed to be integrated into /harness-standards and /prevc before delegation. - Use Case: Before dispatching a generator subagent to implement a feature, apply the matrix so it can edit only scoped files while bash commands require confirmation. ## Quick Start Apply the harness agent permissions matrix to assign safe role-based permissions to my planner, generator, evaluator, and security reviewer subagents before delegation.

Frequently Asked Questions about harness-agent-permissions

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

FAQPage Schema
How do I set permissions for OpenCode agents and subagents?

Use a role-based permission matrix that maps each agent role to explicit rules for read, edit, bash, task, and external_directory access. Apply the matrix before delegation so each subagent operates within its defined scope.

What permissions should a code generator agent have?

A generator agent should have read access allowed, edit access scoped to its assigned files, bash set to ask for confirmation, task allowed, and external directory access denied. This limits unintended changes outside its scope.

Can evaluator agents run bash commands safely?

Yes, evaluators can be allowed to run targeted checks via bash while edit access stays denied. This lets them validate code through tests and checks without modifying the codebase.

Should agents have access to external directories?

No, external directory access should be denied by default for all roles including planners, generators, evaluators, and security reviewers. This prevents agents from reading or modifying files outside the project boundary.

When should I apply the permission matrix in a workflow?

Apply the matrix before any delegation happens, integrating it into your harness standards and PREVC workflow. Setting permissions upfront ensures every subagent starts with the correct constraints rather than relying on defaults.