allow-agent-commands
Add or change allowed commands in AI agent permission configs (OpenCode, Claude Code)
Best use case
allow-agent-commands is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Add or change allowed commands in AI agent permission configs (OpenCode, Claude Code)
Teams using allow-agent-commands should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/allow-agent-commands/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How allow-agent-commands Compares
| Feature / Agent | allow-agent-commands | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Add or change allowed commands in AI agent permission configs (OpenCode, Claude Code)
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# 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: ```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 Configuration File: `.claude/settings.json` under `permissions.allow` Format: ```json "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: 1. Find their config file (usually in `~/.config/` or project root) 2. Look for `permissions`, `allowedCommands`, or similar sections 3. Add the command with glob patterns for arguments 4. **Insert new entries in alphabetical order by command name** 5. **Do NOT reorder existing entries.** ## After Adding Commands After 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 ## Examples Adding `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:*)", ```
Related Skills
xlsx-to-csv
Convert XLSX spreadsheets (single or multi-sheet) to CSV files you can read and grep. Use whenever you need to process an .xlsx report from Xero, Cryptio, bank exports, or any tool that delivers spreadsheet output.
xero-mcp
Use the Xero MCP server — obtain/refresh OAuth2 bearer tokens, troubleshoot authentication, and pick up other operational notes for working with Xero MCP tools. Use when Xero MCP tools fail with authentication errors, when the bearer token has expired (tokens last ~30 min), before starting any Xero workflow, or for general guidance on Xero MCP usage.
xero-browser
General Xero browser automation notes. Use when automating any Xero page with agent-browser — covers non-standard UI patterns, waiting, and dropdown menus.
test-running
Run tests according to repository guidelines. Use after linting passes, before staging changes.
task-orchestration
Orchestrate the complete development workflow for implementing sub-tasks from a task list. Use for end-to-end feature implementation with quality controls.
task-implementation
Implement a single sub-task from a task list. Use when working on feature development with existing task lists.
task-generation
Generate a detailed task list from a PRP. Use after a PRP is created and ready for implementation planning.
subagent-authoring
Create subagent definitions for Claude Code and OpenCode that delegate to skills. Use when creating new subagents or refactoring existing ones to follow the delegation pattern.
slow-command-running
Pipe long running commands through tee(1) to allow watching output and repeated analyses without rerunning
skill-authoring
Create and maintain Claude Code skills following Anthropic best practices. Use when building new skills, refactoring existing ones, or ensuring skills follow official guidelines for structure, naming, progressive disclosure, and testing.
safe-rm
Safely delete files / directories without asking for permission
prp-generation
Generate a Product Requirements Prompt (PRP) from a feature description. Use when starting work on a new feature.