google-qr-sms-helper

Chrome Extension (MV3) to switch Google's mandatory QR code verification back to standard 6-digit SMS verification via iPad Mini profile & [3,null,4] RPC fallback.

Runs with mockssource: GitHubJavaScriptMITcommit 5ea1fd6d1480

JavaScript, MIT licensed. The project labels itself: browser automation, chrome extension, google auth, manifest v3 and sms verification.

google-qr-sms-helper runs, with stand-ins for the services it depends on. An Argusic agent installed it in 0.5 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.

Google QR SMS Helper Chrome extension v1.1.0 (MV3) loads successfully in Chrome 127. UA spoofing produces iPad Mini identity on accounts.google.com. Background worker has declarativeNetRequest header-modification rules and RPC-based QR-to-SMS downgrade logic. Content script injects UI panel and communicates with background. All source files are valid JavaScript.

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.10 (measured)
recorded runs
1
last tested
stars
264
forks
60
open issues
6
watchers
1
size
0 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.

Install time
under a minute
Cold machine to finish
5 minutes
Errors hit and fixed
0 hit, 0 fixed with no human help
How the result was proved
Loaded extension in puppeteer with Chrome 127.0.6533.88 (headless, --no-sandbox). navigator.userAgent returned iPad Mini UA, navigator.platform=ipad, navigator.vendor=Apple Computer Inc, maxTouchPoints=5. All JS files parsed without syntax errors. Manifest permissions verified.
Model tokens used
58,432
Exact commit tested
5ea1fd6d1480
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.

Here's a summary of what was done and observed:
**Project**: Google QR SMS Helper — a Chrome extension (MV3) that downgrades Google's QR-code verif…
**Installation**: No build step required (it's a Chrome extension with unpacked source files). I in…
**Verification**:
- All 3 JS files (`background.js`, `content.js`, `ua_spoof.js`) parse as valid JavaScript
- `manifest.json` is valid JSON with MV3, proper permissions (`declarativeNetRequest`, `scripting`,…
- Extension loaded successfully into Chrome 127 (headless, `--no-sandbox`)
- `ua_spoof.js` content script works: `navigator.userAgent` returns iPad Mini UA, `navigator.platfo…
- `background.js` correctly sets up `declarativeNetRequest` header-modification rules and RPC handl…
- `content.js` creates the UI panel, uses `BarcodeDetector` API, and communicates with the backgrou…
- The asset PNG (`cloud-shell-verify.png`) is valid
The extension is a fully functional Chrome MV3 extension. It cannot be fully end-to-end tested with…

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 0.5 minutes, faster than the median of the 14 comparable projects Argusic has measured.
  • Nothing broke on the way: zero errors between clone and running.
  • Licensed MIT, 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 15 browser-automation projects Argusic has installed and timed, google-qr-sms-helper was the 1st fastest to reach a running state, and 13 of 15 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.10

Topics (from GitHub)

browser-automationchrome-extensiongoogle-authmanifest-v3sms-verification

Embed the badge

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

[![Tested by Argusic](https://argusic.com/badge/google-qr-sms-helper.svg)](https://argusic.com/subject/google-qr-sms-helper)

Questions

Does google-qr-sms-helper run?
google-qr-sms-helper runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 1 minutes, hitting 0 errors on the way, and recorded the session.
How did Argusic test google-qr-sms-helper?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 5ea1fd6d1480. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test google-qr-sms-helper?
The run that produced this verdict cost $0.10: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does google-qr-sms-helper take to install?
0.5 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 google-qr-sms-helper need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing google-qr-sms-helper?
Nothing did, in the recorded run: zero errors between clone and running.
How does google-qr-sms-helper compare with the alternatives?
Of the 15 browser-automation projects Argusic has installed and timed, google-qr-sms-helper was the 1st fastest to reach a running state, and 13 of 15 reached one at all.
Where is the evidence for google-qr-sms-helper?
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