agent-lint
CLI tool for cost estimation and anti-pattern detection in agent workflow YAML configs. Catch expensive, fragile, or ungoverned agent workflows before they hit production.
The Problem
Agent workflows fail in predictable ways: unbounded loops, no retry limits, missing cost guards, parallel branches with no coordination. Most teams find these problems in production — after a $400 API bill or a stuck workflow that ran for six hours.
agent-lint finds them at config time.
Install
pip install agentlinter
Usage
# Lint a single workflow config
agent-lint lint workflow.yaml
# Lint all workflows in a directory, fail CI if score < 80
agent-lint lint workflows/ --fail-under 80
# Estimate token/cost exposure for a workflow
agent-lint estimate workflow.yaml --provider anthropic
# Generate a full audit report
agent-lint lint workflows/ --format markdown
# Suggest autofixes as a diff patch
agent-lint lint workflow.yaml --fix
What It Detects
Anti-patterns:
- Unbounded retry loops (no max_retries or timeout)
- Missing cost guards on high-token operations
- Parallel agent branches with no merge strategy
- Hard-coded API keys in config (security)
- Missing checkpointing on long-running workflows
- Agents with no defined output schema
Cost estimation:
- Token budget projection per workflow step
- Worst-case / expected-case / best-case cost ranges
- Model-aware pricing (Claude, GPT-5.6, and self-hosted Ollama models)
Scoring:
- 0-100 score per workflow
- Error (-15 pts), warning (-5 pts), info (-1 pt)
- CI integration:
--fail-underthreshold
CI Integration
- uses: actions/checkout@v4
- uses: AreteDriver/agent-lint@v0.4.0
with:
path: workflows/
fail-under: 80
Treat your agent configs like production code. Gate them the same way.
Licensing & Tiers
agent-lint is available in two tiers:
Free — Always free, no license key required:
lint— anti-pattern detectionestimate— token/cost estimationstatus— show version and tier info
Pro — Unlock additional features with a license key:
compare— compare costs across providers side-by-side- Markdown export for audit reports
- Custom pricing tables
- Custom rule packs
- Historical tracking and trend analysis
Activate Pro with an environment variable:
export AGENT_LINT_LICENSE=ALNT-XXXX-XXXX-XXXX
Why Static Analysis
No LLM dependency. No API calls. No variance between runs. Agent configs are deterministic artifacts — they should be audited deterministically.
Status
- Anti-pattern detection (17 rules)
- Cost estimation (Claude, GPT-5.6, legacy OpenAI, and Ollama)
- CI integration with threshold gating
- Markdown audit reports
- SARIF output for GitHub Advanced Security
- GitHub PR annotation format
- Autofix diff generation (
--fix) - Docker images (multi-arch)
- Gemini pricing model
- VS Code extension
Related Projects
- mcp-manager — MCP server manager with built-in audit (
pip install arete-mcp) - ai-spend — Cost observability for the workflows agent-lint guards (
pip install ai-spend) - animus — The AI operating environment with built-in quality gates and eval pipeline
Part of the AreteDriver AI tooling ecosystem.
Metadata
Release files for agentlinter 0.4.0
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 |
|---|---|---|---|---|
| agentlinter-0.4.0.tar.gz | 102.8 kB | With provenance | Details for agentlinter-0.4.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| agentlinter-0.4.0-py3-none-any.whl | Python 3 | none | any | Details for agentlinter-0.4.0-py3-none-any.whl |
Total release size: 150.6 kB
Release files / agentlinter-0.4.0.tar.gz
| Download URL | agentlinter-0.4.0.tar.gz |
|---|---|
| Size | 102.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8ffbf3f9f5ae0776ee9b98df7d6fa3740cf824be38f66163dcd631cf7dcd3d6c
|
|
BLAKE2b-256 checksum How to use checksums |
6dce0c32a866953818dabd9da9616e98c08de8d4f0afb64ad60ee2fecf5b2415
|
| 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 Aug 24, 2026.
Transparency logRelease files / agentlinter-0.4.0-py3-none-any.whl
| Download URL | agentlinter-0.4.0-py3-none-any.whl |
|---|---|
| Size | 47.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
26510cfd3842d3929d074646b022e5f1b4a2133c438aa3d3e13fdf9c65403657
|
|
BLAKE2b-256 checksum How to use checksums |
d1f1a056510022bb894f6be5ff819e99a89a1d28c5b28edfbf33e335ba436855
|
| 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 Aug 24, 2026.
Transparency logSecurity for agentlinter 0.4.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 2 files in this release have been uploaded with provenance metadata.
Attestation for agentlinter-0.4.0.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 Aug 24, 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.