CyberStrikeAI
The system of action for AI-native cybersecurity, where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.
Runs with mockssource: GitHubGoApache-2.0commit 470eb5ead185
Go, Apache-2.0 licensed. The project labels itself: ai, ai agents, ai cybersecurity, ai hacking, ai penetration testing, ai security tool, ctf tools and mcp.
CyberStrikeAI runs, with stand-ins for the services it depends on. An Argusic agent installed it in 15 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 CyberStrikeAI binary builds cleanly with Go 1.25.0, serves its web UI on HTTP port 8080 with a 200 status, accepts admin login via POST /api/auth/login returning a full permissions token, and all 28 internal Go test packages (including database, handler, multiagent, security, mcp, and workflow) pass without failures.
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
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.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Go 1.25.0 not found on system PATH (only Python 3.12.3 was pre-installed)3 minutes
- Install time
- 15 minutes
- Cold machine to finish
- 17 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- curl http://127.0.0.1:8080/ returned 200; POST /api/auth/login with bootstrap admin password returned full admin token and permissions; go test ./internal/... exited 0, 28 packages passed
- Model tokens used
- 53,790
- Exact commit tested
- 470eb5ead185
- 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.
exec /bin/sh -lc 'cd /work/repo && export PATH=/home/runner/go25/go/bin:$PATH && go test ./cmd/... 2>&1 … succeeded in 4056ms: ? cyberstrike-ai/cmd/mcp-stdio [no test files] ? cyberstrike-ai/cmd/server [no test files] ? cyberstrike-ai/cmd/test-config [no test files] ? cyberstrike-ai/cmd/test-external-mcp [no test files] ? cyberstrike-ai/cmd/test-sse-mcp-server [no test files] All tests pass — 28 internal packages with test files all reported `ok`, zero failures. Here's the … tokens used 53,790 All tests pass — 28 internal packages with test files all reported `ok`, zero failures. Here's the …
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 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.
- Took 15 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 ai projects Argusic has installed and timed, CyberStrikeAI was the 51st fastest to reach a running state, and 49 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 by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.05 |
Topics (from GitHub)
aiai-agentsai-cybersecurityai-hackingai-penetration-testingai-security-toolctf-toolsmcppentesting-tools
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/cyberstrikeai)Questions
- Does CyberStrikeAI run?
- CyberStrikeAI runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 15 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test CyberStrikeAI?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 470eb5ead185. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test CyberStrikeAI?
- The run that produced this verdict cost $0.05: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does CyberStrikeAI take to install?
- 15 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 CyberStrikeAI need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing CyberStrikeAI?
- 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 CyberStrikeAI compare with the alternatives?
- Of the 64 ai projects Argusic has installed and timed, CyberStrikeAI was the 51st fastest to reach a running state, and 49 of 64 reached one at all.
- Where is the evidence for CyberStrikeAI?
- 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.