js-reverse-automation--skill

结合chrome-devtools-mcp的能力并加上Skill的规范,实现JSRPC+Flask+autoDecoder方案的前端JS逆向自动化分析,提升JS逆向的效率

Runs with mockssource: GitHubPythonApache-2.0commit 61e6e47b0fc1

Python, Apache-2.0 licensed. The project labels itself: ai tools, automation, burp suite, javascript, js, js reverse, reverse and reverse engineering.

js-reverse-automation--skill runs, with stand-ins for the services it depends on. An Argusic agent installed it in 2.3 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

The project installs cleanly in a venv, all 22 Python/JS scripts run successfully, the Flask proxy generates and starts, and validate_artifacts passes all schema/syntax/cross-file checks, only browser-dependent features (Chrome, JSRPC live server, real target website) remain untested in this container.

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 92 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs with mocks
Argusic Score
92 / 100
cost of the verifying run
$0.06 (measured)
recorded runs
1
last tested
stars
616
forks
84
open issues
0
watchers
4
size
1 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing js-reverse-automation--skill, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • wrapped_headers referenced before assignment in generated Flask proxy1.5 minutes
Install time
2 minutes
Cold machine to finish
4 minutes
Errors hit and fixed
1 hit, 1 fixed with no human help
How the result was proved
ran validate_artifacts.py on generated artifacts: 11/11 checks passed; Flask proxy starts and returns 200 on direct POST; all 6 generated JS files pass Node syntax check; doctor.py reports all deps OK
Model tokens used
72,408
Exact commit tested
61e6e47b0fc1
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
Behaviour against real services
this run was verified against stand-in services only

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

| `check_delivery_contract.py` | passed — endpoint normalization, packet modes, wrapper |
| `validate_artifacts.py` | ✅ all 11 checks passed |
| `validate_browser_evidence.py` | OK (with session data) |
| `hook_templates.py` | OK |
| `adversarial_diff.py` | OK |
| `quarantine.py` | OK |
| `env_patcher.py` | ran (expected gaps w/o real browser) |
| `manage_services.py` | OK |
| Flask proxy (live) | 200 on direct POST, 502 on wrapper mode (expected — no real JSRPC) |
| All generated JS | 6/6 syntax-valid via Node |
| JS scripts CLI | `source_instrumentor.js`, `ast_candidate_analyzer.js` parse and show their help |
**What can't be verified in this container**: Real browser-based end-to-end tests need Chrome (not …

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Installed in 2.3 minutes, faster than the median of the 26 comparable projects Argusic has measured.
  • Recovered from all 1 error without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed Apache-2.0, as reported by its host.

What did not, or is not known

  • Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 27 ai-tools projects Argusic has installed and timed, js-reverse-automation--skill was the 13th fastest to reach a running state, and 19 of 27 reached one at all.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs with mocks92.000.06

Topics (from GitHub)

ai-toolsautomationburp-suitejavascriptjsjs-reversereversereverse-engineeringsecurity-toolsskillsweb-security

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/js-reverse-automation--skill.svg)](https://argusic.com/subject/js-reverse-automation-skill)

Questions

Does js-reverse-automation--skill run?
js-reverse-automation--skill runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 2 minutes, hitting 1 error on the way, and recorded the session.
How did Argusic test js-reverse-automation--skill?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 61e6e47b0fc1. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test js-reverse-automation--skill?
The run that produced this verdict cost $0.06: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does js-reverse-automation--skill take to install?
2.3 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does js-reverse-automation--skill need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing js-reverse-automation--skill?
1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does js-reverse-automation--skill compare with the alternatives?
Of the 27 ai-tools projects Argusic has installed and timed, js-reverse-automation--skill was the 13th fastest to reach a running state, and 19 of 27 reached one at all.
Where is the evidence for js-reverse-automation--skill?
The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion