agentic_security

Agentic LLM Vulnerability Scanner / AI red teaming kit 🧪

Runssource: GitHubhomepagePythonApache-2.0commit b9755a9ead2f

Python, Apache-2.0 licensed. The project labels itself: agent framework, agent security, ai red team, llm evaluation, llm evaluation framework, llm fuzzer, llm fuzzer aggregator and llm fuzzing.

agentic_security runs. An Argusic agent installed it in 6 minutes and hit 6 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

The agentic-security package installs on Python 3.12, the CLI --help displays usage, the FastAPI health endpoint returns 200, the CI scan command runs successfully against a local self-probe endpoint, and 390 of 390 selected tests pass with zero 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 100 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.12 (measured)
recorded runs
2
last tested
stars
2,047
forks
314
open issues
22
watchers
24
size
24 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 agentic_security, 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.

  • Forward type annotations (e.g. -> Scan, -> AttackRuleSeverity) fail on Python <3.142 minutes
  • sklearn OneClassSVM model pickled with old version lacks _effective_probability attr1.5 minutes
  • pyproject.toml requires Python >=3.14 but container has 3.12 only1 minute
  • Missing test deps inline-snapshot and pytest-mock1 minute
  • except json.JSONDecodeError, TypeError: needs parentheses in Python 3.120.5 minutes
  • System test subprocess Popen('uvicorn') fails because uvicorn not on PATH
Install time
6 minutes
Cold machine to finish
6 minutes
Errors hit and fixed
6 hit, 6 fixed with no human help
How the result was proved
pytest tests/ returned 390 passed, 3 skipped, 41 deselected; GET /health -> 200 {"status":"ok"}; agentic_security --help prints CLI usage; SecurityScanner.scan() executed a real scan against the self-probe endpoint and produced module results
Model tokens used
63,275
Exact commit tested
b9755a9ead2f
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

Watch the session

The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.

A recording of attempt 1, run . The verdict above comes from a different attempt, so read this as one session and not as the current result. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.

The end of the recording

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

end = time.time()
print(f'"'import time: {end-start:.3f}s')
\" 2>&1 | grep -v \""'^INFO'"\\|"'^WARNING'"\\|DeprecationWarning\" | head -5" in /work/repo
 succeeded in 2201ms:
         agentic_security.toml.
import time: 1.967s
All fixed and verified. Here's the final report:
**ARGUSIC_RESULT:** {"install_succeeded": true, "launch_succeeded": true, "install_minutes": 6, "er…
tokens used
63,275
All fixed and verified. Here's the final report:
**ARGUSIC_RESULT:** {"install_succeeded": true, "launch_succeeded": true, "install_minutes": 6, "er…

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

  • Reached a running state on a clean machine, with the session recorded.
  • Recovered from all 6 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Ran without a GPU, so it does not need one to start.
  • Licensed Apache-2.0, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

  • Took 6 minutes to install, slower than the median of the 62 comparable projects Argusic has measured.

Of the 63 agent-framework projects Argusic has installed and timed, agentic_security was the 45th fastest to reach a running state, and 50 of 63 reached one at all.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.
  • A quick evaluation: it was running 6 minutes after the clone.

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 Runner2/3Runs100.000.12
Argusic Runner1/3Runs100.000.12

Topics (from GitHub)

agent-frameworkagent-securityai-red-teamllm-evaluationllm-evaluation-frameworkllm-fuzzerllm-fuzzer-aggregatorllm-fuzzingllm-guardrailsllm-jailbreaksllm-scannerllm-securityllm-vulnerabilitiesprompt-testing

Embed the badge

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

[![Tested by Argusic](https://argusic.com/badge/agentic_security.svg)](https://argusic.com/subject/agentic-security)

Questions

Does agentic_security run?
Yes. agentic_security runs. Argusic installed and launched it on a clean machine in 6 minutes, hitting 6 errors on the way, and recorded the session.
How did Argusic test agentic_security?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit b9755a9ead2f. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test agentic_security?
The run that produced this verdict cost $0.12: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does agentic_security take to install?
6 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 agentic_security need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing agentic_security?
6 things broke in the recorded run, and 6 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does agentic_security compare with the alternatives?
Of the 63 agent-framework projects Argusic has installed and timed, agentic_security was the 45th fastest to reach a running state, and 50 of 63 reached one at all.
Where is the evidence for agentic_security?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion