Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/onewave-ai/claudecodeunleashed/regex-debuggernpx skills add OneWave-AI/ClaudeCodeUnleashed --skill regex-debuggergit clone --depth 1 https://github.com/OneWave-AI/ClaudeCodeUnleashedWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/onewave-ai/claudecodeunleashed/regex-debugger)<a href="https://agentmods.dev/skills/onewave-ai/claudecodeunleashed/regex-debugger"><img src="https://agentmods.dev/badge/skills/onewave-ai/claudecodeunleashed/regex-debugger.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00038 | $0.01346 |
| Opus 5 | $0.00019 | $0.00673 |
| Sonnet 5 | $0.00008 | $0.00269 |
| Haiku 4.5 | $0.00004 | $0.00135 |
Grade A, and why
regex-visual-debugger scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Regex Visual Debugger
Interactive regex testing, explanation, and debugging tool.
When to Use This Skill
Activate when the user:
- Provides a regex pattern to debug
- Asks "why isn't my regex working?"
- Needs a regex pattern explained
- Wants to test regex against strings
- Asks to convert regex between flavors (Python, JS, etc.)
- Needs regex pattern suggestions
- Mentions regular expressions or pattern matching
Instructions
-
Analyze the Regex Pattern
- Parse the regex structure
- Identify each component (groups, quantifiers, character classes)
- Check for common syntax errors
- Validate regex syntax for specified flavor
-
Provide Plain English Explanation
- Break down pattern piece by piece
- Explain what each part matches
- Describe overall pattern behavior
- Clarify quantifier greediness
- Explain capture groups vs. non-capturing groups
-
Visual Breakdown
- Show pattern structure hierarchically
- Highlight groups and alternations
- Indicate character classes and ranges
- Mark anchors and boundaries
-
Test Against Examples
- Test provided test strings
- Show what matches and what doesn't
- Highlight matched portions
- Explain why matches succeed or fail
- Show capture group contents
-
Identify Common Issues
- Unescaped special characters
- Incorrect quantifiers
- Greedy vs. non-greedy issues
- Anchor misplacement
- Unclosed groups
- Flavor-specific incompatibilities
-
Generate Test Cases
- Create strings that should match
- Create strings that should NOT match
- Include edge cases
- Test boundary conditions
-
Suggest Improvements
- More efficient patterns
- More readable alternatives
- Performance optimizations
- Edge case handling
-
Convert Between Flavors
- Python (re module)
- JavaScript
- Perl
- Java
- .NET
- PHP (PCRE)
Output Format
# Regex Analysis: `pattern`
## Plain English Explanation
This pattern matches [description]:
- `^` - Start of string
- `[A-Z]` - One uppercase letter
- `\d{3}` - Exactly 3 digits
- `$` - End of string
**Overall**: Matches strings like "A123", "Z999"
## Visual Structure
^ - Start anchor [A-Z] - Character class (uppercase letters) \d{3} - Digit, exactly 3 times $ - End anchor
## Test Results
### ✅ Matches
- `A123` → ✓ Full match
- `Z999` → ✓ Full match
### ❌ No Match
- `a123` → ✗ Lowercase 'a' doesn't match [A-Z]
- `A12` → ✗ Only 2 digits (needs 3)
- `A1234` → ✗ Too many digits
## Capture Groups
1. Group 1: `[captured text]`
2. Group 2: `[captured text]`
## Issues Found
⚠️ **Issue 1**: Pattern is too restrictive
- **Problem**: Doesn't handle lowercase letters
- **Fix**: Use `[A-Za-z]` instead of `[A-Z]`
## Suggested Improvements
```regex
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 4d ago First seen · 194 lines · 38 tokens per session scan A f8a10923acb3
regex-visual-debugger is a skill published in the GitHub repository OneWave-AI/ClaudeCodeUnleashed (5 stars, last pushed 6mo ago), licensed MIT. It adds 38 tokens to every session and 1,346 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…