A workflow for investigating how web front ends work internally, including request signatures, encrypted parameters, cookies, browser checks, and obfuscated JavaScript. It can also guide reproducing observed behavior outside the browser.

Use it to analyze request authentication, anti-bot fields, encrypted data, workers, WebAssembly, browser hooks, source maps, and JavaScript behavior that needs to be reproduced.

It helps turn difficult-to-read browser code and network behavior into testable findings instead of relying on guesses or incomplete clues.

web-reverse — Skill for Codex by JacksonTai2007/cc-unlock

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 JacksonTai2007/cc-unlock --skill web-reverse

Clone the repo

git clone --depth 1 https://github.com/JacksonTai2007/cc-unlock

Made for: 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/jacksontai2007/cc-unlock/web-reverse/github.svg)](https://agentmods.dev/skills/jacksontai2007/cc-unlock/web-reverse)

Your own site

<a href="https://agentmods.dev/skills/jacksontai2007/cc-unlock/web-reverse"><img src="https://agentmods.dev/badge/skills/jacksontai2007/cc-unlock/web-reverse/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/jacksontai2007/cc-unlock/web-reverse"><img src="https://agentmods.dev/badge/skills/jacksontai2007/cc-unlock/web-reverse.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 138 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 7,606 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. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

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.

Model	Per session	Once invoked
Fable 5.1	$0.00138	$0.07606
Opus 5.5	$0.00055	$0.03042
Sonnet 5.5	$0.00028	$0.01521
Haiku 4.5	$0.00014	$0.00761

Measured 23d ago against content hash 9920cb379afa, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

web-reverse 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 23d ago.

The scan reads SKILL.md. This mod also ships 7 executable files (artifacts/tasks/_TEMPLATE/core/run/closeout.mjs, artifacts/tasks/_TEMPLATE/core/run/run-local.mjs, artifacts/tasks/_TEMPLATE/core/run/validate-fixture.mjs, …), 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.

cc-unlock-files/skill-bundle/sec-forge/web-reverse/SKILL.md · 227 lines

How it starts

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

Web Reverse

这是一个任务契约驱动的总控 + 路由系统，不是知识清单。本文件只做三件事：锁定验收目标、约束执行节奏、把任务路由到正确的 reference / workflow。细则一律按需读 references/ 与 docs/reference/（见末尾路由表）。

约束力来自机制而非文字篇幅，要优先消灭三种失效模式：

目标漂移：用户要 A，执行中偷偷降成 B，还把 B 说成完成。
虚假完成：没过最终验证就说"已完成 / 已交付"。局部样本、单点成功、容器可读、浏览器偶发成功都不算验收。
线索不落盘：发现了线索只放在脑子里 → 任务一中断就得重新分析，白烧 token。

何时使用

还原签名/认证参数/挑战链/风控字段；分析混淆 JS、动态代码、source map、反调试、反篡改；分析 Worker/iframe/多上下文、JSVMP/自定义 VM/WASM/媒体解密；基于浏览器证据做 Node/Python 复现、纯算法迁移、浏览器内可控复用；或继续已有 task-local 任务。

不适用：普通前端开发、密码学教学、漏洞利用 / 渗透或其它非 Web 前端逆向。

北极星：以验收为唯一目标

目标不是持续汇报新发现，而是在任务契约下尽快逼近用户验收目标。每个动作前先自问：① 用户最终交付是什么；② 这个动作是否直接缩短到该交付；③ 当前路线是否还值得再走一轮。研究型收敛 ≠ 交付型推进。

逆向中你通常不知道哪条路最短，直到走通。所以发现线索的第一反应是「记录」而不是「立刻写脚本验证」——验证可能失败、可能被打断，只有落盘的线索能跨轮复用（见下文「记录与搜索」）。

三条红线（其余都是指引，唯这三条不可退让）

先初始化再动手：任何分析 / 浏览器操作 / 写文件前，先在当前项目目录执行 node $TOOL_DIR/task-boot.mjs <task-id>（幂等：有任务则续跑，无则新建）。 $TOOL_DIR = 本 skill 包内 tools/task/ 的绝对路径；优先使用宿主技能目录给出的实际 SKILL.md 路径，不从项目 cwd 向上猜测技能位置。只在首次使用或路径失效时解析（见 docs/reference/tooling-degradation.md Step 0），后续调用复用已确认路径及预检结果。task-boot.mjs 通过自身 import.meta.url 定位工具，内部已串起 task-init（新建）/ resume → task-sync → task-advance，无需重复手调或每轮重测环境。 每个 workspace 只在首个动作前 boot 一次：续跑时直接按 task-advance 输出的 nextExecutableAction 执行，不要每轮重复 boot。boot 的 ready 输出会打印产物写入锚点的绝对路径（run/ / state/ / report.md），照它写。跳过它产物会散落根目录、状态无法跨轮恢复。Windows 路径用正斜杠。细则见 docs/reference/startup-gate-procedures.md。
产物落 task 目录：本任务产生的每个文件（脚本/样本/中间数据/报告）都落在 cwd 下 artifacts/tasks/<task-id>/（脚本与样本进 run/，状态进 state/，报告就是 report.md）。 cwd 根只允许项目元文件（SKILL.md / README.md / .gitignore / package.json / package-lock.json 等，以及 tsconfig.json / vite.config.* / requirements.txt 等常见构建配置；完整白名单真源 = tools/task/common.mjs 的 WORKSPACE_ROOT_ALLOWLIST，门禁与本表共用），其余逆向脚本/数据一律进 artifacts/tasks/。 这条红线有机械门禁：task-close / verify-once 会扫描 workspace 根目录，凡是本任务 boot 之后新增的非白名单 .js/.mjs/.cjs/.ts/.py/.json/.jsonl 文件一律 BLOCK（rule=move-stray-artifacts-into-task-run-dir）；task-close 还会自动把它们 [relocate] 进 run/。不要靠"我觉得放根目录也行"——门禁不认。
完成必须可验证："已完成 / 已成功 / 已交付"只能在 run/verify-once.mjs 真跑通、 run/fixtures.json 存在、acceptanceGap 为空后才能说。交付物 = 验证脚本跑通的副产品，不是口头宣称。 assert-can-reply 返回 BLOCKED（exit≠0）就等于「未完成」：此时禁止任何用户可见的交付性回复（包括"已完成/已闭环/已实现"的总结、表头标"已验证"、贴成功结论），只能继续执行它打印的 nextExecutableAction；复述 BLOCKED 原因、或把 BLOCKED 包装成"基本完成/已基本跑通"都不算交付，仍属违规。 挑战链 / 验证码 / 滑块类任务（模式 A）的验收 = 端到端服务端返回成功（如求解器实际通过、error==0 且业务校验通过），不是「格式被接受 / JSON 字段齐全 / validate-fixture 通过」——validate-fixture.mjs 只校验 JSON 字段存在，绝不能冒充验收；这类成功必须由 run/verify-once.mjs 复现，未复现前 claimLevel 最高只能停在 provisional。

Read the full file on GitHub · 227 lines

Files

What ships with it

60 files 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.

23d ago Changed 9920cb379afa
1mo ago First seen · 227 lines · 138 tokens per session scan A 8b24c7743d5c

Subscribe to this mod's changes

web-reverse is a skill published in the GitHub repository JacksonTai2007/cc-unlock (167 stars, last pushed 23d ago), licensed MIT. It adds 138 tokens to every session and 7,606 once invoked, about $0.0006 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.

Debugging Security

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