[BUG] plugin-dev:command-development skill fails to load - false positive on bash security check 🐞
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
The plugin-dev:command-development skill cannot be loaded. When invoked, Claude Code's bash security validation incorrectly flags a documentation example within the skill's SKILL.md file as dangerous.
The pattern echo "$1" in a markdown code block is being misinterpreted as bash locale quoting ($"..." syntax), triggering a security check that blocks the entire skill from loading.
What Should Happen?
The skill should load successfully. Documentation examples within SKILL.md files should not trigger bash security validation - only actual executable bash patterns should be validated.
Error Messages/Logs
Error: Bash command permission check failed for pattern "!`echo "$1" | grep -E "^(dev|staging|prod)$" || echo "INVALID"`": Command contains locale quoting which can hide characters
Steps to Reproduce
- Install the plugin-dev plugin:
````
/plugin install plugin-dev@claude-plugins-official
- Invoke the command-development skill:
````
/plugin-dev:command-development
- Observe the error message about "locale quoting which can hide characters"
Note: The problematic content is a documentation example in the skill's SKILL.md file (approximately line 763):
Validate environment: !`echo "$1" | grep -E "^(dev|staging|prod)$" || echo "INVALID"`
The security regex /\$"[^"]*"/ matches $"1" within "$1" because the $ character appears immediately before a ", even though this is just a shell variable reference inside double quotes, not bash locale quoting.
Claude Model
Opus
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
2.1.1 (Claude Code)
Platform
Anthropic API
Operating System
Ubuntu/Debian Linux
Terminal/Shell
Cursor
Additional Information
_No response_
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗