llm-gate — Claude Code skill: what it does, how to install
llm-gate configures prompt and agent hooks in Claude Code to validate commit messages, stop dangerous terminal commands, and catch secret leaks before execution.
MIT ★ 2,966 updated 2026-09-29
/plugin marketplace add rohitg00/pro-workflow
/plugin install pro-workflow@pro-workflowWhat llm-gate does
This skill guides the setup of type: "prompt" and type: "agent" hooks inside Claude Code. These hooks intercept actions during events like PreToolUse. They inject command arguments into a small model such as Haiku, expecting a JSON reply with an ok status. If the check fails, Claude Code blocks the tool execution immediately.
The provided patterns cover conventional commit enforcement, guardrails against rm -rf on critical directories, and secret scanning on write operations. More complex audits, such as scanning staged diffs before git push, run under agent hooks with a 60-second timeout.
Keep hook prompts under 100 words to maintain evaluation speed and consistent JSON output.
What it helps with
- validate commit messages against conventional commit standards
- block destructive bash commands on core directories
- stop file writes containing unencrypted API keys and tokens
- inspect staged code for vulnerabilities prior to git push
Example prompts for the agent
- Set up a prompt hook to enforce conventional commits with Haiku
- Create a PreToolUse hook preventing destructive rm commands
- Configure an agent hook to audit security before git push
How to install llm-gate
1Plugin marketplace
/plugin marketplace add rohitg00/pro-workflow/plugin install pro-workflow@pro-workflowThis installs the whole pro-workflow plugin with all its skills
2Skills CLI (Vercel)
npx skills add rohitg00/pro-workflow --skill llm-gate -a claude-code3Manually: put the files in place
~/.claude/skills/llm-gate/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/llm-gate/
1Skills CLI (Vercel)
npx skills add rohitg00/pro-workflow --skill llm-gate -a codex2Manually: put the files in place
.agents/skills/llm-gate/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add rohitg00/pro-workflow --skill llm-gate -a cursor2Manually: put the files in place
.cursor/skills/llm-gate/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install rohitg00/pro-workflow skills/llm-gate2Manually: put the files in place
.github/skills/llm-gate/SKILL.md1Skills CLI (Vercel)
npx skills add rohitg00/pro-workflow --skill llm-gate -a gemini-cli2Platform CLI
gemini skills install https://github.com/rohitg00/pro-workflow --path skills/llm-gateManually: put the files in place
.devin/skills/llm-gate/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about llm-gate
How to install llm-gate in Claude Code?
Run /plugin marketplace add rohitg00/pro-workflow first, then run /plugin install pro-workflow@pro-workflow.
What does llm-gate do?
It provides patterns for prompt-based guardrails in hooks.json to verify tool calls using small LLMs before execution.
Which model should prompt hooks use?
Haiku is recommended for fast checks under 15 seconds, while Sonnet fits heavier agent reviews with timeouts up to 60 seconds.
Source text
SKILL.md · MIT
---
name: llm-gate
description: LLM-powered quality verification using prompt hooks. Validates commit messages, code patterns, and conventions using AI before allowing operations. Use to set up intelligent guardrails.
---
# LLM Gate
Use Claude Code's `type: "prompt"` hooks to create intelligent quality gates that use AI to verify operations.
## Trigger
Use when:
- Setting up commit message validation
- Enforcing code conventions beyond what linters catch
- Creating smart guardrails for specific operations
## How Prompt Hooks Work
Claude Code supports hooks with `type: "prompt"` that run a small LLM (Haiku by default) to verify conditions:
```json
{
"PreToolUse": [{
"matcher": "Bash",
"hooks": [{
"type": "prompt",
"if": "Bash(git commit*)",
"prompt": "Check if this git commit follows conventional commit format (<type>(<scope>): <summary>). The commit command is: $ARGUMENTS. Return {\"ok\": true} if valid, {\"ok\": false, \"reason\": \"...\"} if not.",
"model": "haiku",
"timeout": 15
}]
}]
}
```
The hook:
1. Substitutes `$ARGUMENTS` with the JSON hook input
2. Sends to Haiku (fast, cheap)
3. Expects `{"ok": true}` or `{"ok": false, "reason": "..."}`
4. If not ok → blocks the tool call with the reason
## Example Gates
### Conventional Commit Validator
```json
{
"type": "prompt",
"if": "Bash(git commit*)",
"prompt": "Verify this git commit follows conventional commits: type(scope): summary. Types: feat,fix,refactor,test,docs,chore,perf,ci. Summary under 72 chars. Input: $ARGUMENTS",
"model": "haiku"
}
```
### Destructive Command Guard
```json
{
"type": "prompt",
"if": "Bash(rm *)",
"prompt": "Check if this rm command is safe. Flag if it uses -rf on important directories (src/, node_modules/, .git/). Input: $ARGUMENTS",
"model": "haiku"
}
```
### API Key Leak Prevention
```json
{
"type": "prompt",
"matcher": "Write",
"prompt": "Check if this file write contains hardcoded API keys, secrets, passwords, or tokens. Input: $ARGUMENTS. Return ok:false if secrets found.",
"model": "haiku"
}
```
## Agent Hooks
For complex verification, use `type: "agent"` (runs a full agent):
```json
{
"type": "agent",
"if": "Bash(git push*)",
"prompt": "Review all staged changes for security issues before pushing. Check for: hardcoded secrets, SQL injection, XSS vulnerabilities, exposed internal URLs.",
"model": "haiku",
"timeout": 60
}
```
## Setup Guide
1. Choose which operations to gate
2. Write the prompt (keep it focused, under 100 words)
3. Pick the model (haiku for speed, sonnet for accuracy)
4. Set timeout (15s for prompts, 60s for agents)
5. Add to hooks.json under the appropriate event
## Rules
- Use Haiku for simple checks (fast, cheap)
- Use Sonnet only for complex analysis
- Keep prompts under 100 words for reliability
- Always include `if` condition to avoid running on every tool call
- Set reasonable timeouts (15s prompt, 60s agent)
- Test hooks before deploying to avoid blocking workflows
© Rohit Ghumare · MIT · rohitg00/pro-workflow