vizra-adk

Build, test, and deploy intelligent AI agents the Laravel way

Runs with mockssource: GitHubPHPMITcommit dc5f302ac0d5

PHP, MIT licensed. The project labels itself: agent framework, ai, ai agents, ai tools, anthropic, autonomous agents, gemini and laravel.

vizra-adk runs, with stand-ins for the services it depends on. An Argusic agent installed it in 8 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

PHP 8.4.26 and Composer 2.10.3 installed via static binaries, all 136 Composer dependencies resolved and autoloaded, and the Pest test suite passes fully (1084/1084 passing tests) using SQLite in-memory database and mock LLM providers

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.07 (measured)
recorded runs
1
last tested
stars
295
forks
37
open issues
3
watchers
7
size
2 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 vizra-adk, 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.

  • PHP 8.2+ not installed — missing entirely from container1 minute
  • Composer not installed1 minute
Install time
8 minutes
Cold machine to finish
9 minutes
Errors hit and fixed
2 hit, 2 fixed with no human help
How the result was proved
php vendor/bin/pest --no-coverage exited 0, 1084 passed, 9 skipped (browser-only tests), 0 failed, 2822 assertions across 83 test suites
Model tokens used
69,181
Exact commit tested
dc5f302ac0d5
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.

php /work/repo/vendor/bin/pest --version 2>&1 | head -1' in /work/repo
 succeeded in 0ms:
Start time check:
Sun Oct 25 22:24:22 UTC 2026
/home/runner/bin/php
PHP 8.4.26 (cli) (built: Oct  5 2026 06:34:19) (NTS x86_64-linux-musl-gcc)
Copyright (c) The PHP Group
/work/repo/vendor/autoload.php
Here's my final summary:
tokens used
69,181
Here's my final summary:

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

  • Recovered from all 2 errors without a human stepping in, which says the failures are documented well enough to solve.
  • 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.
  • Took 8 minutes to install, slower than the median of the 63 comparable projects Argusic has measured.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 64 agent-framework projects Argusic has installed and timed, vizra-adk was the 49th fastest to reach a running state, and 51 of 64 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.07

Topics (from GitHub)

agent-frameworkaiai-agentsai-toolsanthropicautonomous-agentsgeminilaravellaravel-packagellmopenaiphp

Embed the badge

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

[![Tested by Argusic](https://argusic.com/badge/vizra-adk.svg)](https://argusic.com/subject/vizra-adk)

Questions

Does vizra-adk run?
vizra-adk runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 8 minutes, hitting 2 errors on the way, and recorded the session.
How did Argusic test vizra-adk?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit dc5f302ac0d5. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test vizra-adk?
The run that produced this verdict cost $0.07: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does vizra-adk take to install?
8 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 vizra-adk need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing vizra-adk?
2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does vizra-adk compare with the alternatives?
Of the 64 agent-framework projects Argusic has installed and timed, vizra-adk was the 49th fastest to reach a running state, and 51 of 64 reached one at all.
Where is the evidence for vizra-adk?
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