permission-manager – Coding skill for AI agents
Manage opencode permissions: review always-allow lists, suggest safe read-only commands, configure permission patterns
Install the permission-manager skill with one command
Pick the tool you use, copy the command and paste it in your terminal. The skill lands in that tool's skills folder and is ready in your next session.
Claude Code
mkdir -p ~/.claude/skills && curl -fsSL https://skill.dn1nguoi.com/z/permission-manager-80254.tgz | tar xz -C ~/.claude/skills
Call it in Claude Code: /permission-manager – then describe the task you want done.
Codex
mkdir -p ~/.codex/skills && curl -fsSL https://skill.dn1nguoi.com/z/permission-manager-80254.tgz | tar xz -C ~/.codex/skills
Call it in Codex: $permission-manager – then describe the task you want done.
Hermes Agent
mkdir -p ~/.hermes/skills && curl -fsSL https://skill.dn1nguoi.com/z/permission-manager-80254.tgz | tar xz -C ~/.hermes/skills
Call it in Hermes Agent: /permission-manager – then describe the task you want done.
DeepSeek
mkdir -p ~/.deepcode/skills && curl -fsSL https://skill.dn1nguoi.com/z/permission-manager-80254.tgz | tar xz -C ~/.deepcode/skills
Call it in DeepSeek: /permission-manager – then describe the task you want done.
SKILL.md content
What I do
- Review and summarize currently always-allowed commands
- Suggest safe read-only commands for auto-approval
- Add or remove commands from the allow list in opencode.json
- Configure skill-level permissions (allow/deny/ask) with wildcard patterns
- Audit permission configs for security and usability
When to Use
Use this when optimizing opencode's permission settings, reviewing allowed commands, or configuring skill access controls.
Workflow Steps
1. Read current config: Load ~/.config/opencode/opencode.json or project-level opencode.json
2. Summarize permissions: Identify currently allowed commands and skill permissions
3. Suggest additions: Propose safe read-only commands for auto-allow (see recommended list below)
4. Apply changes: Edit the config to add/remove permission entries
5. Validate: Ensure JSON is valid after changes
Complements opencode's built-in allow/deny/ask permissions by auditing current config and recommending adjustments through conversation.
Key Rules
- Never allow commands that modify files, commit, push, or change system state
- Prefer exact command entries such as
git status --short,git diff --stat, andls -la - Avoid trailing wildcards such as
git status*unless the expanded command family has been manually reviewed as read-only - Confirm with user before modifying permission config
- Distinguish between bash command permissions and skill permissions
- Keep config organized: group related commands together
Limitations
- This skill is scoped to opencode permission configuration and should not modify other agent hosts' permission stores.
- Treat all write-capable command permissions as high-risk; review them manually even when a pattern looks narrow.
How to trigger me
Use the Task tool with the permission-manager subagent type:
/permissionsOr in natural language, ask opencode to "manage opencode permissions" or "review allowed commands".
Related skills
- phase-gated-debugging – Use when debugging any bug. Enforces a 5-phase protocol where code edits are blocked…
- php – Language-specific super-code guidelines for php.
- pi-delegate – Delegate coding tasks to the Pi coding agent CLI (`pi`) only when the user explicitly…
- placecall – Place real outbound phone calls to US businesses through the PlaceCall API: book, ask…
- plaid-fintech – Expert patterns for Plaid API integration including Link token flows, transactions sync…
- platform-engineering – Build internal developer platforms (IDPs) with self-service infrastructure, golden…
- playwright-java – Scaffold, write, debug, and enhance enterprise-grade Playwright E2E tests in Java using…
- poka-yoke – Mistake-proof code, config and process: make the wrong action impossible or…