How do I install the Allow Agent Commands skill?

Run npx skillmds@latest add aspiers/allow-agent-commands in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Allow Agent Commands safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Allow Agent Commands?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Allow Agent Commands free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Allow Agent Commands?

aspiers (@aspiers) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Allow Agent Commands by aspiers — Agent Skill

Name: Allow Agent Commands
Rating: 4.5 (4 reviews)
Author: aspiers

Allow Agent Commands

Adds or changes allowed commands in AI agent permission configs for OpenCode and Claude Code. Use when a command needs adding to an agent's allow list, when permission settings for existing commands need changing, when setting up a new AI tool that requires command permissions, or when the user asks to stop being prompted for a particular command.

aspiers 13435bd 2.7 KB Updated Sep 10, 2026

File contents

Adding/Changing Allowed Commands

When to use this skill

Use this skill when:

A command needs to be added to the allow list for AI agents
Permission settings need to be modified for existing commands
Setting up a new AI tool that requires command permissions

How it works

Commands must be explicitly allowed in the permission configs before agents can run them. This skill covers adding entries to both OpenCode and Claude Code configuration files.

IMPORTANT: The config files are stowed into ~ via GNU Stow symlinks. Always edit them directly from within the ai-config repository, NOT from ~. The paths below are relative to the ai-config repository root.

OpenCode Configuration

File: .config/opencode/opencode.json under permission.bash

Format:

"uname *": "allow",

Pattern: "command argpatterns": "action" where * matches any args

Important: Insert new entries in alphabetical order by command name. When adding a new command, find the correct position to maintain sorting. Do NOT reorder existing entries.

Claude Code Configuration

File: .claude/settings.json under permissions.allow

Format:

"Bash(uname:*)",

Important: Insert new entries in alphabetical order. Commands are sorted by the command name (the part after Bash( and before :). Do NOT reorder existing entries.

General Pattern for New AI Tools

When adding new AI tools:

Find their config file (usually in ~/.config/ or project root)
Look for permissions, allowedCommands, or similar sections
Add the command with glob patterns for arguments
Insert new entries in alphabetical order by command name
Do NOT reorder existing entries.

After Adding Commands

After adding the new command entries to both config files:

Check if there are any other staged changes with git status
If there are NO other staged changes, stage ONLY the new hunks in the two config files using the git-stager subagent (be careful not to stage unrelated changes)
Invoke the git-committer subagent to commit the changes

Examples

Adding rg (ripgrep) to both configs:

OpenCode (insert after rev *, before rpm -q*):

"rg *": "allow",

Claude Code (insert after Bash(rg:*), before Bash(rpm -q:*)):

"Bash(rg:*)",

---name: allow-agent-commandsdescription: Adds or changes allowed commands in AI agent permission configs for OpenCode and Claude Code. Use when a command needs adding to an agent's allow list, when permission settings for existing commands need changing, when setting up a new AI tool that requires command permissions, or when the user asks to stop being prompted for a particular command.---# Adding/Changing Allowed Commands## When to use this skillUse this skill when:- A command needs to be added to the allow list for AI agents- Permission settings need to be modified for existing commands- Setting up a new AI tool that requires command permissions## How it worksCommands must be explicitly allowed in the permission configs before agentscan run them. This skill covers adding entries to both OpenCode and ClaudeCode configuration files.**IMPORTANT**: The config files are stowed into `~` via GNU Stow symlinks.Always edit them directly from within the ai-config repository, NOT from `~`.The paths below are relative to the ai-config repository root.## OpenCode ConfigurationFile: `.config/opencode/opencode.json` under `permission.bash`Format:```json"uname *": "allow",```Pattern: `"command argpatterns": "action"` where `*` matches any args**Important**: Insert new entries in alphabetical order by command name.When adding a new command, find the correct position to maintain sorting.**Do NOT reorder existing entries.**## Claude Code ConfigurationFile: `.claude/settings.json` under `permissions.allow`Format:```json"Bash(uname:*)",```**Important**: Insert new entries in alphabetical order. Commands are sortedby the command name (the part after `Bash(` and before `:`).**Do NOT reorder existing entries.**## General Pattern for New AI ToolsWhen adding new AI tools:1. Find their config file (usually in `~/.config/` or project root)2. Look for `permissions`, `allowedCommands`, or similar sections3. Add the command with glob patterns for arguments4. **Insert new entries in alphabetical order by command name**5. **Do NOT reorder existing entries.**## After Adding CommandsAfter adding the new command entries to both config files:1. Check if there are any other staged changes with `git status`2. If there are NO other staged changes, stage ONLY the new hunks in the two config files using the `git-stager` subagent (be careful not to stage unrelated changes)3. Invoke the `git-committer` subagent to commit the changes## ExamplesAdding `rg` (ripgrep) to both configs:**OpenCode** (insert after `rev *`, before `rpm -q*`):```json"rg *": "allow",```**Claude Code** (insert after `Bash(rg:*)`, before `Bash(rpm -q:*)`):```json"Bash(rg:*)",```

Frequently asked questions