AgentGuard CLI
Security testing for AI agents, before production. agentguard performs an offline
static check or evaluates an agent through an AgentGuard control plane, prints an honest
verdict, and exits non-zero when a deploy must be blocked or coverage is incomplete.
The judgement is deterministic (never an LLM deciding what's a vulnerability) and reproducible: the same configuration always yields the same verdict, explainable to the engineer it blocks at 2am.
Install
pip install agentguard-dev
The CLI has two lightweight dependencies (httpx and PyYAML). Offline static checks need
no API key, network, database, or control plane.
First local check
agentguard init
agentguard scan --local
Static mode validates the manifest, declared policies, and accidental credentials. It does
not execute a model, so behavioural scenarios are reported as SKIPPED and the command
exits 40 (INCOMPLETE). To explicitly accept a static-only partial gate in CI:
agentguard scan --local --allow-incomplete-static --sarif agentguard.sarif
Behaviour simulation through a control plane
export AGENTGUARD_API_KEY=ag_your_key_here # from your org's onboarding
agentguard scan \
--api-url https://your-agentguard-host \
--agent my-support-bot \
--manifest manifest.json \
--environment prod \
--html report.html
Exit codes are the CI contract:
| Code | Meaning |
|---|---|
0 |
allowed |
20 |
blocked (a scenario failed at blocking severity) |
10 |
error |
30 |
unknown (could not evaluate — fail closed) |
40 |
incomplete (behavioural coverage was not run) |
--html report.html writes a self-contained report (no external requests) with the
verdict, evidence, and a per-finding remediation.
Compute a fingerprint locally
agentguard fingerprint --manifest manifest.json
The fingerprint identifies an exact agent configuration; a verdict is bound to it, so v2 never inherits v1's pass.
More
agentguard --help lists every command. Full docs and the control-plane setup live in the
repository.
Release files for agentguard-dev 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| agentguard_dev-0.1.1.tar.gz | 35.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| agentguard_dev-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 75.0 kB
Release files / agentguard_dev-0.1.1.tar.gz
| Download URL | agentguard_dev-0.1.1.tar.gz |
|---|---|
| Size | 35.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c93c0fd50534c6de4473ad622c20c5e864462491e254702c438fc1332886b37e
|
|
BLAKE2b-256 checksum How to use checksums |
30969db7930f3ff2a555c0c67e0487695f4bcca2e64c3ac54b53981847fa642f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 31, 2026.
Transparency logRelease files / agentguard_dev-0.1.1-py3-none-any.whl
| Download URL | agentguard_dev-0.1.1-py3-none-any.whl |
|---|---|
| Size | 39.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bc3a0f0163ea3f15098c77459d5ca207c1ce727c1ef2cf1fb8e0dfdfb838ee22
|
|
BLAKE2b-256 checksum How to use checksums |
f50aab641b5a203a5362dc06574513a1fc0027d99afcee12de079812dfb84100
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 31, 2026.
Transparency log