skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
mskadu/opencode-agent-skills65 installs

permission-manager

Manage opencode permissions: review always-allow lists, suggest safe read-only commands, configure permission patterns

How do I install this agent skill?

npx skills add https://github.com/mskadu/opencode-agent-skills --skill permission-manager
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubfail

    This skill is designed to manage the agent's security configuration by reading and writing to the 'opencode.json' permission file. This allows for the modification of 'always-allow' lists, which can be used to bypass user confirmation for sensitive or dangerous operations.

  • Socketpass

    No alerts

  • Snykwarn

    Risk: MEDIUM · 1 issue

What does this agent skill do?

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 me

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
  • Use wildcards appropriately (e.g., git status* not just git status)
  • Confirm with user before modifying permission config
  • Distinguish between bash command permissions and skill permissions
  • Keep config organized: group related commands together

How to trigger me

Use the Task tool with the permission-manager subagent type:

/permissions

Or in natural language, ask opencode to "manage opencode permissions" or "review allowed commands".

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/mskadu/opencode-agent-skills/permission-manager">View permission-manager on skillZs</a>