Agent Engineering Toolkit
Your coding agent says tests passed. AET proves which code was actually tested.
AET provides proof-carrying workflows for coding agents. It binds test runs, changed files, artifacts, and agent claims into portable evidence, then tells you when that proof no longer applies.
Try the stale-proof demo
After v1.18.0 is published:
uvx --from agent-engineering-toolkit aet demo stale-proof
Expected result:
1. Test command executed PASS
2. Proof matches the tested source EXACT_MATCH
3. Source changed without rerunning tests RELEVANT_FILES_CHANGED
Demo result: PASS
The test really passed. Then a relevant source file changed without rerunning it, so AET correctly stopped applying the old proof to the current code.
The demo is local and deterministic after package download. It uses Git and
Python's standard-library unittest; it makes zero network or LLM calls.
Install
uv tool install agent-engineering-toolkit
aet --version
The PyPI package currently remains at v1.11.1. Do not advertise the v1.18 demo command until PyPI or the exact GitHub Release wheel is verified.
Choose the smallest surface
| Question | Command |
|---|---|
| Are Agent instructions usable? | aet quick check . |
| Does a diff fit the task? | aet quick scope . --base main --intent aet.intent.json |
| Did this command run on these files? | aet quick proof --output proof.json --relevant-path src/app.py -- <argv> |
| Does old proof still apply? | aet quick fresh --proof proof.json |
| What should change without editing? | aet plan context ... |
AET is not another coding agent. It does not replace tests or CI, turn missing
evidence into PASS, or auto-edit, commit, push, merge, or release.
Python 3.11+ · MIT License · no product telemetry
1 maintainer
Metadata
1 maintainer
Release files for agent-engineering-toolkit 1.18.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| agent_engineering_toolkit-1.18.0-py3-none-any.whl | Python 3 | none | any | Details for agent_engineering_toolkit-1.18.0-py3-none-any.whl |
Release files / agent_engineering_toolkit-1.18.0-py3-none-any.whl
| Download URL | agent_engineering_toolkit-1.18.0-py3-none-any.whl |
|---|---|
| Size | 1.4 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9b6000ebd8e6cf9d174f1fb6797cf7299cf9246a5adcacd6c16033a63bd24f76
|
|
BLAKE2b-256 checksum How to use checksums |
092ab841d8a6b05f09939653303d14603c8279367c39907488e3ec9bb0c19632
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.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 29, 2026.
Transparency logSecurity for agent-engineering-toolkit 1.18.0
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
All 1 file in this release has been uploaded with provenance metadata.
Attestation for agent_engineering_toolkit-1.18.0-py3-none-any.whl
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 29, 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.
