allow-agent-commands

Modify permission configurations to control AI agent commands in OpenCode and Claude Code.

15|2|Updated Aug 16, 2025
One-click install
npx skills add https://github.com/aspiers/ai-config --skill allow-agent-commands
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: allow-agent-commands
Source: https://github.com/aspiers/ai-config/tree/main/.claude/skills/allow-agent-commands
Command: npx skills add https://github.com/aspiers/ai-config --skill allow-agent-commands

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Add or change allowed commands in AI agent permission configs (OpenCode, Claude Code).

Core Features & Use Cases

  • Manage permission entries across both configuration files to ensure consistent access control.
  • Enforce alphabetical ordering when adding new commands and coordinate with staging and committing workflows.
  • Use Case: Onboard a new tool by updating permissions in .config/opencode/opencode.json and .claude/settings.json, then stage and commit changes.

Quick Start

Edit the relevant configuration files to add the new command in alphabetical order and use the git-stager and git-committer subagents to finalize the change.

Frequently Asked Questions about allow-agent-commands

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

FAQPage Schema
How do I add allowed commands to AI agent permission configs?

Add allowed commands to AI agent permission configs by editing the configuration files for Claude Code and OpenCode. New commands must be inserted in alphabetical order to maintain a consistent and auditable permission list.

How do I update Claude Code and OpenCode settings to allow new agent commands?

Update Claude Code and OpenCode settings by modifying the permission entries in the respective configuration files. Coordinating these changes ensures consistent access control across both platforms for new tool integrations.

What is the best way to manage AI agent command permissions across multiple platforms?

Managing AI agent command permissions across multiple platforms involves updating the allowed command lists in each platform's configuration file. This approach maintains safe, auditable permission lists and coordinates changes via git subagents.

Can I use git to stage and commit AI agent permission config changes?

You can use git to stage and commit AI agent permission config changes by utilizing git-stager and git-committer subagents. This workflow finalizes the configuration updates after adding new commands in alphabetical order.

Why does the order of allowed commands matter in AI agent configuration files?

The order of allowed commands matters in AI agent configuration files because enforcing alphabetical ordering maintains safe, auditable permission lists. This structured approach prevents disorganized entries when onboarding new tools or applying policy changes.