agentleFS
Sign inStart free
lushun2014lushun2014/lushibo-skills/js-reverse/SKILL.md

js-reverse

Skill0 starsChanged 29 days agoNo licenceView on GitHub

JavaScript reverse engineering: obfuscation recovery, signature/HMAC location, browser environment patching, and frontend crypto extraction. 在使用 js-reverse-mcp 做前端 JavaScript 逆向时使用，适用于签名链路定位、页面观察取证、运行时采样、本地补环境复现与证据化输出。优先适配当前环境里的 js-reverse_* 工具，需要更强的浏览器/CDP/Hook 面时联动 jshookmcp。

6 other projects use a version of this, 6 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use browser-extension-reverse, cloud-k8s and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • zhaoxuya520Skill

    browser-extension-reverse

    Use for authorized reverse engineering of browser extensions (Chrome/Firefox) including manifest analysis, background workers, and extension-based credential or traffic logic recovery.

    Also in 3 projects that use this

  • zhaoxuya520Skill

    cloud-k8s

    Use for authorized cloud, container, and Kubernetes security assessment including metadata SSRF, IAM misconfig, container escape paths, and cluster RBAC review.

    Also in 3 projects that use this

  • Wang200935Skill

    digital-forensics

    Comprehensive CTF forensics workflows covering file type identification,

    Also in 3 projects that use this

  • Youchu-lawhubSkill

    case-review

    收到裁判文书后的研析与复盘——三级覆盖：庭审复盘（庭后五维效果分析）、裁判文书研析报告（主体/诉请与判决/请求权/事实查明/说理/裁判结果六维 + 逐页比对事实认定与证据采信、提炼胜败因）、结案复盘报告（结案报告十项 + 四维反思）。两种深度：自办案件（调取台账/事实梳理/过程文书做深度复盘）与非自办/受限信息（仅基于用户提供的裁判文书与有限信息），输出面向客户/法务领导/业务部门汇报。触发词：复盘、裁判文书分析、判决分析、研析判决、结案报告、结案复盘、办案总结、庭审复盘、败诉分析。

    Also in 3 projects that use this

  • conjure-3301Skill

    email-security

    DNS-level email authentication (SPF/DKIM/DMARC) exploitation, mail infrastructure attacks, relay abuse, and domain verification gaps — the infrastructure layer beneath email header injection

    Also in 3 projects that use this

  • +7 more from zhaoxuya520

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free