T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:1- Finding
Read-Only Skill Declares Unrestricted Bash Access
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is mostly an advisory automation recommender, but it asks for broad shell access and recommends powerful automated Claude workflows without enough guardrails.
Review this skill before installing. It is not clearly malicious, but treat its recommendations as powerful automation templates: remove or constrain Bash if you want read-only behavior, do not run headless Edit/Write workflows without review, do not pipe model output directly into commands, pin package tools, and avoid committing secret-bearing MCP configs.
SKILL.md:1Read-Only Skill Declares Unrestricted Bash Access
references/skills-reference.md:185Unpinned npx Command Can Retrieve and Execute Dependency Code
Skill contains instructions that could directly expose system prompts, internal rules, or hidden instructions to users or external parties.
**This skill is read-only.** It analyzes the codebase and outputs recommendations. It does NOT create or modify any files. Users implement the recommendations themselves or ask Claude separately to help build them.
## Output Guidelines
- **Recommend 1-2 of each type**: Don't overwhelm - surface the top 1-2 most valuable automations per category
- **If user asks for a specific type**: Focus only on that type and provide more options (3-5 recommendations)
The skill includes explicit guidance to invoke Claude in headless mode with write-capable tools (Edit,Write) for automated remediation. Even though framed as an example, this normalizes delegated autonomous code modification and can be repurposed in CI or hooks to make unsupervised changes from prompts, increasing the risk of prompt injection, unsafe edits, or policy bypass through automation chains.
# Pre-commit hook example
claude -p "fix lint errors in src/" --allowedTools Edit,Write
# CI pipeline with structured output
claude -p "<prompt>" --output-format stream-json | your_command
The streamed headless invocation pattern enables external automation pipelines to consume model output directly and act on it, potentially without sufficient validation or human review. In a recommendation skill, this expands the role from advisory analysis toward orchestrating autonomous model-driven workflows, which can magnify prompt-injection and supply-chain risks when integrated into CI or shell pipelines.
claude -p "fix lint errors in src/" --allowedTools Edit,Write
claude -p "" --output-format stream-json | your_command
### Permissions for Hooks
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
| Detection | Presence Of |
|-----------|-------------|
| `.env`, `.env.local`, `.env.production` | Environment files |
| `credentials.json`, `secrets.yaml` | Secret files |
| `.git/` directory | Git internals |
**Recommend**: PreToolUse hook that blocks Edit/Write to these paths
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
| Detection | Presence Of |
|-----------|-------------|
| `.env`, `.env.local`, `.env.production` | Environment files |
| `credentials.json`, `secrets.yaml` | Secret files |
| `.git/` directory | Git internals |
**Recommend**: PreToolUse hook that blocks Edit/Write to these paths
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
| Ruff/Black config | Auto-format Python |
| tsconfig.json | Type-check on Edit |
| Test directory | Run related tests on Edit |
| .env files | Block .env edits |
| Lock files | Block lock file edits |
| Go project | gofmt on Edit |
| Rust project | rustfmt on Edit |
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
| Ruff/Black config | Auto-format Python |
| tsconfig.json | Type-check on Edit |
| Test directory | Run related tests on Edit |
| .env files | Block .env edits |
| Lock files | Block lock file edits |
| Go project | gofmt on Edit |
| Rust project | rustfmt on Edit |
The activation text is broad enough to match many generic requests about improving Claude Code usage, which increases the chance this skill is invoked when a more narrowly scoped skill would be safer or more appropriate. Overbroad auto-selection can expose more tools and instructions than necessary, increasing attack surface and the likelihood of unintended behavior.
The file presents the skill as read-only, but later content recommends write-capable automations, hook permissions, and command patterns that enable editing or execution by Claude. This mismatch can mislead users or policy engines about operational risk and cause the skill to be used in contexts where only passive analysis was intended.
The skill claims to analyze the local codebase with the declared toolset, but it instructs the agent to use web search, which expands data sources and trust boundaries beyond what the user may expect. That can lead to recommendations influenced by untrusted external content or hidden tool assumptions, creating integrity and privacy risks during analysis.
Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.
See [references/skills-reference.md](references/skills-reference.md) for details.
Create skills in `.claude/skills/<name>/SKILL.md`. Some are also available via plugins:
| Codebase Signal | Skill | Plugin |
|-----------------|-------|--------|
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
# Hooks Recommendations
Hooks automatically run commands in response to Claude Code events. They're ideal for enforcement and automation that should happen consistently.
**Note**: These are common patterns. Use web search to find hooks for tools/frameworks not listed here to recommend the best hooks for the user.
The document recommends checking .mcp.json into git for team-wide sharing, but it does not warn that MCP configuration may contain sensitive server endpoints, auth settings, or references to locally trusted tools. In a skill that advises automation setup, this can normalize unsafe sharing patterns and lead teams to accidentally commit credentials or expose powerful integrations across the repository.
Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.
# Skills Recommendations
Skills are packaged expertise with workflows, reference materials, and best practices. Create them in `.claude/skills/<name>/SKILL.md`. Skills can be invoked by Claude automatically when relevant, or by users directly with `/skill-name`.
Some pre-built skills are available through official plugins (install via `/plugin install`).
Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.
---
## Custom Project Skills
Create project-specific skills in `.claude/skills/<name>/SKILL.md`.
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
---
name: create-migration
description: Create a database migration file
disable-model-invocation: true
allowed-tools: Read, Write, Bash
---
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
This section recommends subagents with Write and Bash capabilities for test generation and related automation, but it does not warn that these tools can modify repository files or execute system commands. In a skill whose purpose is to recommend automations for a codebase, normalizing powerful tool access without explicit guardrails increases the chance that users enable overly permissive agents and trigger unintended code or environment changes.
The dependency-updater and migration-helper guidance encourages use of Write and Bash for dependency changes and framework migrations but omits warnings about disruptive effects such as lockfile churn, package installation, script execution, configuration drift, or broad refactors. Because these tasks commonly make sweeping project and environment changes, the lack of cautionary language makes unsafe adoption more likely in real repositories.
No suspicious patterns detected.