claude-permissions-optimizer

Generate Bash allowlist patterns from Claude Code session history.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/xbpk3t/ce-codex --skill claude-permissions-optimizer-xbpk3t
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claude-permissions-optimizer
Source: https://github.com/xbpk3t/ce-codex/tree/main/skills/claude-permissions-optimizer
Command: npx skills add https://github.com/xbpk3t/ce-codex --skill claude-permissions-optimizer-xbpk3t

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Many developers experience permission fatigue from repeated Claude Code Bash prompts; this Skill finds frequently used, safe Bash commands in session history and recommends or applies evidence-backed allowlist rules so those commands stop prompting for approval repeatedly.

Core Features & Use Cases

  • Session analysis: Scans Claude Code session transcripts to extract Bash tool usage and counts occurrences across sessions.
  • Normalization & classification: Normalizes commands into stable Bash(...) patterns, classifies them as safe/review/dangerous, and filters already-covered or low-frequency noise.
  • Actionable recommendations & safe apply: Presents a concise summary, numbered safe-to-allow patterns, blocked examples, and then optionally appends approved rules to user or project settings.json with JSON validation and write verification.
  • Use cases: Reduce repeated permission prompts, create an allowlist for common dev workflows, or audit where dangerous commands are being invoked.

Quick Start

Ask the skill to analyze all projects and apply the recommended safe Bash allowlist rules to your user settings.

Frequently Asked Questions about claude-permissions-optimizer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reduce repeated Bash permission prompts in Claude Code?

To reduce Bash permission prompts in Claude Code, analyze your session history to identify frequently used safe commands and generate allowlist patterns for your settings.json. This prevents safe commands from repeatedly requesting approval during development.

How do I create a Bash allowlist from Claude Code session logs?

You can create a Bash allowlist from Claude Code session logs by scanning transcripts to extract tool usage, normalizing commands into stable patterns, and filtering them by safety classification. Safe patterns are then appended to your project or user settings.

Does Claude Code allowlist optimization work with other coding agent transcripts?

Yes, allowlist optimization works with other coding agent transcripts. The extraction scripts analyze recent transcripts across Claude Code sessions and other agents to normalize Bash commands and surface safe patterns for your settings.

How are Bash commands classified when optimizing Claude Code permissions?

Bash commands are classified into safe, review, and dangerous categories during permission optimization. Commands are normalized into stable patterns, filtered to remove already-covered rules and low-frequency noise, leaving only safe-to-allow patterns for review.

Can I automatically apply safe Bash patterns to Claude Code settings.json?

Yes, you can automatically apply safe Bash patterns to Claude Code settings.json. The optimizer optionally appends approved rules to user or project settings with JSON validation and write verification to ensure the configuration is safely updated.

What are the limitations of generating Bash allowlists from session history?

A limitation of generating Bash allowlists from session history is that dangerous commands may still appear in transcripts and require manual review. The tool filters low-frequency noise and already-covered commands, but users must verify safe patterns before applying them to settings.