js-string-decode

js-string-decode is a skill for Claude Code, Codex from batteryshark/rekit. It costs 181 tokens per session (1,413 once invoked), scanned A, original, Apache-2.0.

A static JavaScript decoder for constant-key XOR and character-code string hiding, where text is transformed so it does not appear plainly in the source. It reads the code without running a JavaScript engine.

In plain words
What is it for?
Use it after a scanner finds XOR or character-code hiding, then pass the recovered plaintext to another scanner for investigation.
Why use it?
It reveals hidden strings such as URLs, domains, time zones, or shell commands while avoiding execution of the analyzed code. It is intended for the specific constant-key pattern it supports.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it after a scanner finds XOR or character-code hiding, then pass the recovered plaintext to another scanner for investigation.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/batteryshark/rekit/js-string-decode
Install

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.

Any agent
npx skills add batteryshark/rekit --skill js-string-decode
Clone the repo
git clone --depth 1 https://github.com/batteryshark/rekit

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for js-string-decode

README.md
[![agentmods](https://agentmods.dev/badge/skills/batteryshark/rekit/js-string-decode/github.svg)](https://agentmods.dev/skills/batteryshark/rekit/js-string-decode)
Your own site
<a href="https://agentmods.dev/skills/batteryshark/rekit/js-string-decode"><img src="https://agentmods.dev/badge/skills/batteryshark/rekit/js-string-decode/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.

agentmods 80×15 button for js-string-decode

Your own site · 80×15
<a href="https://agentmods.dev/skills/batteryshark/rekit/js-string-decode"><img src="https://agentmods.dev/badge/skills/batteryshark/rekit/js-string-decode.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 181 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,413 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00181 $0.01413
Opus 5.5 $0.00072 $0.00565
Sonnet 5.5 $0.00036 $0.00283
Haiku 4.5 $0.00018 $0.00141

Measured 1mo ago against content hash 0f295c84c453, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

js-string-decode 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 1mo ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/decode.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/js-string-decode/SKILL.md · 96 lines

How it starts

The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.

JavaScript Constant-Key String Decoder

Statically recover strings that JavaScript hides with a constant-key XOR / charCode scheme, and write them out as plaintext so a downstream scanner can read them. Pure-Python stdlib, read-only — it never runs a JS engine or executes any part of the input.

When to use

A file (often a carved single-file-executable bundle) keeps its telltale strings — C2 URLs, victim domains, timezone names like Asia/Shanghai, shell commands — out of a plain strings dump by XORing each character with a constant byte and reassembling them with String.fromCharCode. js-covert-scan flags that an XOR / charCode tactic is present; this skill decodes it, statically, and hands the plaintext back for rescanning.

It is the zero-execution complement to js-deobfuscate (which recovers encoded string arrays by running the decoder inside a sandbox). Reach for this one when the scheme is the constant-key case and you want no execution at all.

What it does

python3 scripts/decode.py <input.js> [outdir]:

  1. Scan the JS with regex/heuristics (no JS engine, no execution). It finds constant-key XOR/charCode decode sites: a String.fromCharCode(<x> ^ <KEY>) or <c> ^ <KEY> applied over a static encoded literal.
  2. Resolve <KEY> when it is a small int literal (0x91, 145) or a variable assigned a small int nearby (var kk5=91) — best-effort constant propagation by nearest-preceding assignment (so reused minified names resolve to the right scope).
  3. Decode each site (apply the XOR to the encoded data → plaintext).
  4. Write the recovered strings to <outdir>/decoded-strings.js:
    // decoded from <input>
    /* key=91 base64/fn:c57 off=4835057 */ "cn,sankuai.com,netease.com,163.com,…"
    
    one per line as JS string literals, so the fold rescans it as source and sees the plaintext URLs / hostnames / commands.
  5. Emit JSON to stdout (the default — no flag needed):
    {"ok": true, "outputDir": "<abs>", "decoded": [{"key": 91, "count": 2,
      "sample": "cn,sankuai.com,…"}], "siteCount": 2}
    
    Nothing to decode → {"ok": true, "outputDir": "<abs>", "decoded": [], "siteCount": 0}. Bad input → {"ok": false, "error": "…"} and a non-zero exit.

Read the full file on GitHub · 96 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

  1. 1mo ago First seen · 96 lines · 181 tokens per session scan A 0f295c84c453

Subscribe to this mod's changes

js-string-decode is a skill published in the GitHub repository batteryshark/rekit (20 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 181 tokens to every session and 1,413 once invoked, about $0.0007 per session on Opus 5.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-30.

Related

Other skills, from other repositories

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

systematic-debugging

Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.

open-metadata/OpenMetadata · 37 tokens

log-error-digest

Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…

zebbern/claude-code-guide · 71 tokens

deck-retro

Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…

asheshgoplani/agent-deck · 86 tokens

cwv-optimizer

Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…

adobe/skills · 112 tokens

incident-response-incident-response

Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.

rmyndharis/antigravity-skills · 36 tokens