Borrowing it
Nothing to install: this file belongs to divinevideo/divine-mobile. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/divinevideo/divine-mobile/main/.agents/skills/js-regex-cjk-word-boundary/SKILL.mdgit clone --depth 1 https://github.com/divinevideo/divine-mobileWrote 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/divinevideo/divine-mobile/js-regex-cjk-word-boundary)<a href="https://agentmods.dev/skills/divinevideo/divine-mobile/js-regex-cjk-word-boundary"><img src="https://agentmods.dev/badge/skills/divinevideo/divine-mobile/js-regex-cjk-word-boundary/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/divinevideo/divine-mobile/js-regex-cjk-word-boundary"><img src="https://agentmods.dev/badge/skills/divinevideo/divine-mobile/js-regex-cjk-word-boundary.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.1 | $0.00177 | $0.01905 |
| Opus 5 | $0.00088 | $0.00953 |
| Sonnet 5 | $0.00035 | $0.00381 |
| Haiku 4.5 | $0.00018 | $0.00191 |
Grade A, and why
js-regex-cjk-word-boundary 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 8d 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
JavaScript Regex: \b Word Boundary Fails with CJK Characters
Problem
JavaScript's \b (word boundary) assertion silently fails when used with CJK
(Chinese/Japanese/Korean) characters. The regex compiles without error and runs without
throwing, but it simply never matches CJK text that should match. This is particularly
insidious because:
- No error is thrown — the regex just returns
false - The same pattern works perfectly for Latin/ASCII text
- The CJK characters in the pattern are correct (verified by direct string comparison)
Context / Trigger Conditions
- Regex pattern like
/\b\u904B\u8EE2\u514D\u8A31\u8A3C\b/(Japanese: 運転免許証) returnsfalseon text containing the exact characters - Pattern like
/\b\uC6B4\uC804\uBA74\uD5C8\uC99D\b/(Korean: 운전면허증) fails similarly - Text-detection functions (e.g.,
hasDriverLicenceCue(),inferIssuerFromTitleText()) return incorrect results for CJK input while working correctly for all Latin-script patterns - Any regex using
\bboundaries around non-ASCII Unicode characters (also affects Cyrillic, Arabic, Thai, etc.)
Root Cause
JavaScript's \b matches the boundary between a "word character" (\w = [a-zA-Z0-9_]) and
a "non-word character" (\W). CJK characters are classified as \W (non-word characters).
When \b appears before a CJK character, it looks for a \w-to-\W or \W-to-\w
transition. But if the preceding character is also \W (whitespace, punctuation, start of
string, or another CJK character), the boundary condition is \W-to-\W, which \b does
NOT match.
// This FAILS — \b doesn't work with CJK
/\b\u904B\u8EE2\u514D\u8A31\u8A3C\b/.test("運転免許証") // false!
// This WORKS — no word boundaries
/\u904B\u8EE2\u514D\u8A31\u8A3C/.test("運転免許証") // true
Solution
Quick Fix: Remove \b from CJK patterns
Simply remove \b assertions from any regex pattern that matches CJK characters:
// Before (broken):
[/\b\u904B\u8EE2\u514D\u8A31\u8A3C\b/, "JAPAN"], // 運転免許証
[/\b\uC6B4\uC804\uBA74\uD5C8\uC99D\b/, "KOREA"], // 운전면허증
// After (working):
[/\u904B\u8EE2\u514D\u8A31\u8A3C/, "JAPAN"], // 運転免許証
[/\uC6B4\uC804\uBA74\uD5C8\uC99D/, "KOREA"], // 운전면허증
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.
- 8d ago First seen · 147 lines · 177 tokens per session scan A aff01cf9afaf
js-regex-cjk-word-boundary is a skill published in the GitHub repository divinevideo/divine-mobile (264 stars, last pushed today), licensed MPL-2.0. It adds 177 tokens to every session and 1,905 once invoked, about $0.0009 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-09-03.
Other skills, from other repositories
review-all
Multi-agent code review for diffs (project-agnostic). Covers standards, bugs, security, DRY, smells, perf, tests, API contracts, a11y/i18n. Verifies each finding to eliminate false positives. Use for /review-all, pre-PR/pre-commit review, or auditing uncommitted/staged changes.
Network diagnostics
Localize connectivity failures across DNS, routing, NSGs, firewalls, private endpoints, transport, TLS, and application response.
fec-debug-framework
A step-by-step method for finding the cause of front-end build failures, browser errors, broken screens, failed requests, or incorrect data. It separates build, runtime, visual, and API problems and uses evidence to test possible causes.
fec-legacy-to-modern-migration
A guide for moving older front-end code—such as JavaScript, jQuery, HTML/CSS, server-rendered pages, or old frameworks—to newer tools while keeping the same behavior. It covers gradual migrations as well as modernising parts of a multi-page site.
hardening-resilience
Evaluate error handling, i18n, text overflow, and edge cases.
debug-triage
· Triage live outages when the failing component is unknown; localize the fault and route further debugging.