This release is a pre-release and may not be stable for production use.
agenticreq
AgenticReq supports both Specification-Driven Development and Existing-Code Auditing for Agentic AI applications.
agenticreq is a requirements tool for the whole life of an agentic AI project. You can use it in two ways:
- Starting a new project? Write the agent's requirements first. Before any code exists, you write
spec.ymlthe way an SRS is written for traditional software: what the agent must and must not do, who approves what, its limits. Then you build the agent against it, and agenticreq checks the code against the spec as you go. - Already have agentic code? Apply agenticreq to it directly.
agenticreq auditgives findings with no setup,agenticreq initdraws a spec from your code, andagenticreq checkshows where the code does and does not enforce it.
Either way, agenticreq reads the agent's code, without running it, and tells you which requirements the code enforces, which it does not, and which need a person or a test run to confirm. No LLM is called.
agenticreq never suggests numbers. You write them; it checks your code matches.
What it is, and what it is not
| it is | it is not |
|---|---|
| a place to write an agent's requirements before the code: what it must and must not do, who approves what, its limits | a code generator: it writes no agent code |
| a check, while you build and after, that the code matches the spec you wrote | a runtime guardrail: it does not stop the agent while it runs |
| an audit of an agent that already exists, with findings before any spec is written | a security certificate: a clean report is not a guarantee |
| a list of where enforcement is missing, with file and line, plus run evidence from a mock run with no API key | a prompt-injection detector |
It can also export the spec as a policy for OPA or Cedar.
Install
pip install agenticreq
agenticreq version
Python 3.10 or newer, on Windows, Linux and macOS. Installing writes nothing into your project.
Quick start
Run the commands from the agent's folder. agenticreq guide always shows where the folder stands and the next
command.
New project (spec first)
Start before any code exists. Write the requirements, then build the agent against them:
pip install agenticreq # writes nothing into your project
agenticreq init # in the empty folder: writes spec.yml; replace every TODO
# ... build the agent against spec.yml ...
agenticreq check # while you build: compares spec.yml with the code
agenticreq mocks # writes mocks.yml for a test run with mock tools
agenticreq mock-run # runs the agent with a canned model
agenticreq check # reads the run evidence too
agenticreq guide # where this folder stands, and the next command
The spec has three levels:
- Level 1, the project's requirements (you write them):
agent_id,risk_level,goal,out_of_scope,role_boundary,prohibitedtools and actions,approval_required,limits,escalation,untrusted_inputs,data_rules, and the owners (owner,technical_owner).checkreports everyTODOas a gap. - Level 2, the agent-level requirements: agenticreq sets them from
risk_level(yes/no and choice settings only; numbers are always yours). - Level 3, multi-agent systems only:
topology,agent_registry,declared_delegation,conflict_resolution(you write these; the rest have defaults).
What code cannot prove, a person confirms under confirmed: in spec.yml (the sign-off).
Existing project (audit first)
The agent is already built. Start from the code you have:
pip install agenticreq # writes nothing into your project
agenticreq audit # findings immediately: no spec, no setup
agenticreq init # draws spec.yml from the code: a TODO for each decision only you can make
agenticreq check # compares spec.yml with the code
agenticreq mocks # writes mocks.yml for a test run with mock tools
agenticreq mock-run # runs the agent with a canned model
agenticreq check # reads the run evidence too
Then sign off under confirmed: what code cannot prove.
A short spec looks like this:
agent_id: support-agent
risk_level: medium
approval_required:
- {tool: issue_refund, approver: lead@example.com, timeout: 1h, on_timeout: deny}
prohibited:
- {tool: delete_customer, reason: never from a chat}
bounds: {max_steps: 6}
agenticreq params lists every field and its shape.
The 5 steps, the 4 report groups and the exit codes
| step | command | what it does |
|---|---|---|
| 1. audit | agenticreq audit |
quick scan, no spec needed |
| 2. spec | agenticreq init |
writes spec.yml; you replace every TODO |
| 3. check | agenticreq check |
compares spec.yml with the code |
| 4. mock-run | agenticreq mocks, then agenticreq mock-run |
runs the agent with mock tools |
| 5. sign-off | edit confirmed: in spec.yml |
a person confirms what code cannot show |
There is no overall score. Each result lands in one of four groups:
| group | meaning |
|---|---|
| Spec vs code gaps | the spec says X and the code does not do it, or a required field is missing or TODO |
| Human sign-off | only a person can confirm it; answered under confirmed:, never counted as passed |
| Check with a mock run | a run of the agent could show it; each line ends with the next command |
| Passed | read from the code, or seen in every captured run |
| exit code | meaning |
|---|---|
0 |
the --fail-on condition passed (never always exits 0) |
1 |
it failed: gaps (default) a spec vs code gap; all also an open sign-off or a check waiting for a mock run; also when the mock run is older than the code |
2 |
the spec is invalid or missing; nothing was checked |
3 |
no agent or readable code was found; nothing was checked |
Sign-off is a statement, not proof
Some things only a person can confirm, for example that a kill switch exists outside the code. You answer them under
confirmed: in spec.yml:
confirmed:
- clause: kill_switch
answer: yes
by: lead@example.com
date: 2026-11-01
expires: 2027-05-01
evidence: "agent.py:42 checks AGENT_KILL_SWITCH every step"
This is a person's statement on the record. agenticreq checks that the entry is complete, not expired, and that a
file:line in it points at a real line. It does not check what that line says, and it cannot check who wrote by:.
A wrong "yes" closes the item. Treat sign-offs like code review: someone accountable reads them.
reason: and evidence: are interchangeable; write at least one. A value with a comma or a colon must be in quotes.
The mock run
agenticreq mock-run runs your agent with a canned model: no API key, no real LLM, and the network blocked. It
shows which tools the model is offered and in what order. It never shows how a real model would behave.
- Tools that write, pay, send or delete, and tools that reach a database or the network, are replaced in
mocks.yml(patch:+returns:), so the real function never runs. - Writes outside
allow_write:and starting other programs are blocked; the report lists them. - If you change the code after a run, the run's results go back to "Check with a mock run" until you run it again.
- Claude Agent SDK: the SDK runs its own
claudeCLI. The mock run lets only that exact program start and points it at a local canned endpoint (telemetry and updates off). The canned model asks it only for your project's tools and subagents, never for the CLI's own tools (Bash, Write ...). Because the CLI is a separate program, the Python network guard does not cover it. - Use it only on projects you trust: it runs the agent's own code.
Limit the scan
By default the whole folder is scanned. When one folder holds several agents or scripts, scope it:
agenticreq check --entry agent.py # start from agent.py; the files it imports are read too
or in spec.yml:
include: [agent.py]
exclude: [scripts/, "**/batch_*.py"]
The report header says what was scanned.
Limits
- Dynamic agents and factories. Agents and tool lists built at run time (from config, a registry, a loop) cannot always be read from the code. A mock run is the evidence for them; what no run reaches is never a pass.
- Prompt-only code agents. An agent that writes and runs Python as its action (smolagents
CodeAgent) has no tool call to read; its result waits for a mock run and is never a pass. - Transports that cannot be intercepted. The mock run captures model calls made through httpx, requests and aiohttp. A provider reached another way is named ("mock run is not supported for ...") and its items go to sign-off.
- Frameworks whose tool schema cannot carry a numeric cap. A limit on a tool argument is then checked in the tool body; the report says the schema cannot carry it.
- Values only known at run time. A limit read from the command line or an unset environment variable goes to sign-off. A name with several different values in the code is never guessed: it goes to sign-off too.
- MCP only through
--mcp. MCP server tools are seen only with--mcp "<server command>"or--mcp-tools <file>. - Numbers are never suggested (docs/numbers.md).
- Environment variables in the spec are never expanded. A value that is only
$NAMEor${NAME}is reported as a placeholder; text that contains a$is kept exactly as written. - Docker images and remote interpreters are out of scope for the mock run.
Supported frameworks
agenticreq has been tested on a multi-agent project in each of these 15 frameworks, and verified at every step:
audit, init, validate, check, mocks, mock-run, the confirmed: sign-off, and check again
(docs/verification.md has the results).
- LangGraph
- LangChain
- CrewAI
- OpenAI Agents
- Claude Agent SDK
- Google ADK
- smolagents
- AutoGen
- LlamaIndex
- PydanticAI
- Haystack
- Agno
- Semantic Kernel
- DSPy
- Strands
Plain provider SDK code (anthropic, openai, google-genai, groq and other OpenAI-compatible clients) is supported
too. How each framework pauses for a person is listed in src/agenticreq/data/approval_gates.yml, and the framework
versions mock-run was validated on are in src/agenticreq/data/supported_versions.yml.
Platforms
Windows, Linux and macOS. OS-specific behaviour is limited to the mock run:
- Paths are compared case-insensitively on Windows, with long-path (
\\?\) and UNC prefixes understood. - The run gives the agent its own scratch home:
APPDATA/LOCALAPPDATAon Windows,~/Library/...on macOS,XDG_*on Linux. All are created before the run starts. - The platform lookups SDKs make for an OS header (
cmd /c ver,uname,sw_vers) never start a program.
Editor support
agenticreq init writes spec.schema.json next to spec.yml and starts the file with this line, which VS Code and
other yaml-language-server editors read for completion and wrong-field warnings:
# yaml-language-server: $schema=./spec.schema.json
For an existing spec: agenticreq export-schema > spec.schema.json.
More
Architecture · GitHub Action · Numbers · Tools and mock runs · Rules that need a mock run · Contributing · Security · Changelog
License
Apache-2.0.
Metadata
Release files for agenticreq 0.1.0a3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| agenticreq-0.1.0a3.tar.gz | 675.3 kB | With provenance | Details for agenticreq-0.1.0a3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| agenticreq-0.1.0a3-py3-none-any.whl | Python 3 | none | any | Details for agenticreq-0.1.0a3-py3-none-any.whl |
Total release size: 1.1 MB
Release files / agenticreq-0.1.0a3.tar.gz
| Download URL | agenticreq-0.1.0a3.tar.gz |
|---|---|
| Size | 675.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
42328edd9d44feac6c6bf8b4edd9c1b908eb50736295880aee3fd7e7afb0c6e3
|
|
BLAKE2b-256 checksum How to use checksums |
bb0bdc7ee456d65cb3d71ba49dfa36906a3ab59900288bcf8c307d01a0696167
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 15, 2026.
Transparency logRelease files / agenticreq-0.1.0a3-py3-none-any.whl
| Download URL | agenticreq-0.1.0a3-py3-none-any.whl |
|---|---|
| Size | 455.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f636de537e8c5ada89618b13fe234faea8a63444c653fb7481678de2d13593a8
|
|
BLAKE2b-256 checksum How to use checksums |
90aa8e68ec6690eac9559c095942124434923d719cd685a08a0b45ecf9681089
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 15, 2026.
Transparency logSecurity for agenticreq 0.1.0a3
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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for agenticreq-0.1.0a3.tar.gz
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 Nov 15, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.