Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Unicode Boundary Guard

    1

    Prevent silent Unicode corruption across PowerShell, Python, JSON, CDP, and browser forms with exact destination verification.

    Free

    1 useSecurity scanned
    Unicode Boundary Guard

    Unicode Boundary Guard

    Example session with this skill installed

    Enter the name "Nguyễn Văn Duy" into a React-controlled profile field from PowerShell through CDP. Preserve every accent, save the profile, and prove the persisted value is exact before continuing.

    • Read your context and instructions
    • Compiled the unicode boundary guard

    Result

    The first boundary check

    failed safely before submission: the destination contained Nguy?n V?n Duy instead of Nguyễn Văn Duy. Unicode Boundary Guard detected question-mark-substitution, restored the authoritative source, changed the transport to an ASCII-only JSON literal, and verified the fresh saved value.

    GateExpectedActualStatus
    Initial DOM readNguyễn Văn DuyNguy?n V?n DuyFAIL
    Repaired DOM writeNguyễn Văn DuyNguyễn Văn DuyPASS
    Fresh read after saveNguyễn Văn DuyNguyễn Văn DuyPASS
    UTF-8 SHA-256ef76de6e...ffeed9ef76de6e...ffeed9PASS

    Safe transport

    "Nguy\u1ec5n V\u0103n Duy"
    

    Destination proof

    {
      "ok": true,
      "normalization": "exact",
      "expected_sha256_utf8": "ef76de6e80541d696db8e3f41972cade70638f6363d27cac9c67017b33ffeed9",
      "actual_sha256_utf8": "ef76de6e80541d696db8e3f41972cade70638f6363d27cac9c67017b33ffeed9",
      "loss_signals": []
    }
    

    Code-point receipt

    The critical characters were verified as ễ = U+1EC5 and ă = U+0103. The saved profile was then re-opened and compared against the original source.

    Decision: PASS. The next authorized action may continue because the persisted value is exact.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Unicode can be corrupted even when every command returns success. A Windows shell, Python subprocess, JSON payload, CDP expression, or React-controlled input can silently turn a correct name into question marks, replacement characters, or mojibake. Unicode Boundary Guard makes exact destination verification the completion condition.

    What it does

    • Preserves one authoritative expected string before it crosses a tool boundary.
    • Chooses a safe transport: UTF-8 files, utf-8-sig decoding, or ASCII-only JSON literals.
    • Generates React-compatible DOM setters that dispatch input and change events.
    • Compares exact code points and UTF-8 SHA-256 values at source and destination.
    • Detects ?, U+FFFD, mojibake, dropped characters, and unintended normalization.
    • Stops before submit, publish, send, or another external write when verification fails.

    Why it is different

    A success toast only proves that the application accepted an action. This skill reads the destination again and proves that the saved value is identical to the source. The included dependency-free unicode_guard.py utility returns CI-friendly exit codes and ASCII-safe JSON reports.

    Use cases

    • Vietnamese names and localized profile data
    • Multilingual UI copy and emoji
    • PowerShell-to-Python automation
    • JSON and JavaScript generation
    • CDP and browser form automation
    • Database and API write verification

    Known limitations

    The skill requires Python 3 for its deterministic helper. It verifies text integrity but does not grant permission to submit a form or perform another external write.

    Requires Python 3 and the provided utility scripts. Does not authorize final external writes like form submission. Scope is limited to text integrity verification.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    1 use

    Times used to date

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 1 month ago

    • Free with an Agensi account

    Requires

    Node.js

    Permissions

    Terminal / Shell
    Browser
    Read Files

    File Scopes

    **/*.txt
    **/*.json

    Terminal runs the local verifier. Read Files accesses only user-supplied text fixtures. Browser access is used only when the current task already authorizes form inspection or editing; exact verification is required before submit.

    Listed1 month ago

    What's inside

    Frequently Asked Questions

    This skill addresses 'silent corruption' where tools report success while actually mangling text into question marks or mojibake. It verifies that data remains identical at the code-point level after passing through PowerShell, JSON payloads, or browser inputs.

    The package includes the core AI agent logic, the dependency-free `unicode_guard.py` utility for CI/CD integration, and pre-configured React-compatible DOM setters for browser automation.

    Yes, the skill is designed to bridge these environments by generating safe transport formats like ASCII-only JSON literals and UFT-8-sig decoding to ensure text survives Windows-specific shell limitations.

    The skill requires Python 3 for its deterministic verification helper and is compatible with any AI agent capable of executing Python or interacting with the Chrome DevTools Protocol (CDP).

    Unlike standard verification, this skill performs a 'round-trip' check by reading the destination value back and comparing its SHA-256 hash against the source to guarantee 100% data integrity before a final submission.

    New in Testing & Debugging