encoding-toolkit

encoding-toolkit is a skill for Claude Code, Codex from woohyun212/security-skill. It costs 35 tokens per session (1,714 once invoked), scanned A, original, MIT.

A tool for converting text between formats such as Base64, URL encoding, hexadecimal, HTML entities, ROT13, and JWT parts. Encoding changes how data is represented without necessarily changing its meaning.

In plain words
What is it for?
Use it to inspect web requests and responses, examine JWT headers and payloads, solve capture-the-flag challenges, or prepare payloads for web-application firewall testing.
Why use it?
It removes the need to identify and convert encoded strings manually. It helps reveal data hidden behind one or several encoding layers.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/woohyun212/security-skill/encoding-toolkit
Any agent
npx skills add woohyun212/security-skill --skill encoding-toolkit
Clone the repo
git clone --depth 1 https://github.com/woohyun212/security-skill

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 encoding-toolkit

README.md
[![agentmods](https://agentmods.dev/badge/skills/woohyun212/security-skill/encoding-toolkit.svg)](https://agentmods.dev/skills/woohyun212/security-skill/encoding-toolkit)
Your own site
<a href="https://agentmods.dev/skills/woohyun212/security-skill/encoding-toolkit"><img src="https://agentmods.dev/badge/skills/woohyun212/security-skill/encoding-toolkit.svg" alt="Measured on agentmods" height="20"></a>
Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,714 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
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 $0.00035 $0.01714
Opus 5 $0.00017 $0.00857
Sonnet 5 $0.00007 $0.00343
Haiku 4.5 $0.00003 $0.00171

Measured 3d ago against content hash 9cb93e765511, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

encoding-toolkit scanned grade A with 1 finding 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 3d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

import re, base64, urllib.parse, sys
encoding-toolkit/SKILL.md · 224 lines

How it starts

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

What this skill does

Automatically detects the encoding format of an input string and performs encode/decode conversions across Base64, URL encoding, Hex, HTML entities, ROT13, and JWT formats. Uses only standard tools: base64, python3, and xxd.

When to use

  • Analyzing encoded strings found in web requests or responses
  • Stripping multiple encoding layers in CTF challenges
  • Inspecting JWT token headers and payloads
  • Converting payloads into various formats for WAF bypass testing

Prerequisites

  • python3 (uses standard library, no extra installation needed)
  • base64 command (built into Linux/macOS)
  • xxd command (built into Linux/macOS)

Inputs

Variable Description Example
INPUT Input string to convert SGVsbG8gV29ybGQ=
MODE Operation to perform (see list below) base64-decode

Workflow

Step 1: Auto-detect encoding

INPUT="SGVsbG8gV29ybGQ="

echo "=== Auto-detect encoding ==="
python3 - <<PYEOF
import re, base64, urllib.parse, sys

data = """${INPUT}"""

results = []

# Base64 detection
if re.fullmatch(r'[A-Za-z0-9+/]*={0,2}', data) and len(data) % 4 == 0 and len(data) > 0:
    try:
        decoded = base64.b64decode(data).decode('utf-8', errors='replace')
        results.append(f"[Base64 possible] decoded: {decoded[:80]}")
    except Exception:
        pass

# URL encoding detection
if '%' in data:
    try:
        decoded = urllib.parse.unquote(data)
        results.append(f"[URL encoding possible] decoded: {decoded[:80]}")
    except Exception:
        pass

# Hex detection
if re.fullmatch(r'[0-9a-fA-F]+', data) and len(data) % 2 == 0:
    try:
        decoded = bytes.fromhex(data).decode('utf-8', errors='replace')
        results.append(f"[Hex possible] decoded: {decoded[:80]}")
    except Exception:
        pass

# HTML entity detection
if '&' in data and ';' in data:
    import html
    decoded = html.unescape(data)
    results.append(f"[HTML entity possible] decoded: {decoded[:80]}")

# JWT detection
if data.count('.') == 2 and re.match(r'^[A-Za-z0-9_-]+\.[A-Za-z0-9_-]+\.[A-Za-z0-9_-]+$', data):
    results.append("[JWT possible] 3-part dot structure detected -> use Step 4 JWT decode")

if results:
    for r in results:
        print(r)
else:
    print("Auto-detection failed -> specify MODE manually for conversion")
PYEOF

Read the full file on GitHub · 224 lines

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. 3d ago First seen · 224 lines · 35 tokens per session scan A 9cb93e765511

Subscribe to this mod's changes

encoding-toolkit is a skill published in the GitHub repository woohyun212/security-skill (21 stars, last pushed 4mo ago), licensed MIT. It adds 35 tokens to every session and 1,714 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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.

obra/superpowers · 37 tokens

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.

microsoft/vscode · 62 tokens

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.

microsoft/vscode · 51 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens