agentleFS
Sign inStart free
woxiangyangzhimaowoxiangyangzhimao/skills/reverse-traffic-triage/SKILL.md

reverse-traffic-triage

Skill14 starsChanged 4 months agoNo licenceView on GitHub

逆向流量诊断与参数溯源 — 抓到包之后、动手扣代码之前的强制纪律：把目标参数从「请求里出现」一路反查到「在哪段 JS 被写入」。触发词：「抓包」「这个参数哪来的」「定位加密入口」「找不到加密函数」「请求里有个 sign/token 不知道怎么生成」「initiator」「调用栈追踪」「先抓包再说」。当用户已经有了目标请求（HAR/DevTools）、但还没确定加密参数的生成位置时使用。边界：只负责「从流量到加密函数入口」的定位纪律，找到入口后转交 param-encryptor（算法）/ ast-deobfuscation（混淆）/ captcha-solver（验证码）。

Create a free account to mount

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