.agents/skills/allow-agent-commands/SKILL.md
Add or change allowed commands in AI agent permission configs (OpenCode, Claude Code)
npx skillsauth add aspiers/ai-config allow-agent-commandsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use this skill when:
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.
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.
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.
When adding new AI tools:
~/.config/ or project root)permissions, allowedCommands, or similar sectionsAfter adding the new command entries to both config files:
git statusgit-stager subagent (be careful not to stage
unrelated changes)git-committer subagent to commit the changesAdding 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:*)",
development
Run tests according to repository guidelines. Use after linting passes, before staging changes.
development
Orchestrate the complete development workflow for implementing sub-tasks from a task list. Use for end-to-end feature implementation with quality controls.
development
Implement a single sub-task from a task list. Use when working on feature development with existing task lists.
data-ai
Generate a detailed task list from a PRP. Use after a PRP is created and ready for implementation planning.