AGENTS.lock is a package manager for AI agent configurations. It keeps skills, agents, MCP servers, and instructions kept in sync across Claude, Codex, Gemini, and Copilot CLI tools. The lockfile is the single source of truth for both project and global scopes.
Install AGENTS.lock:
pip install agentslock
⚠️ Warning: This is an early release. Breaking changes may occur in future versions.
Usage:
al init # Initialize a new AGENTS.lock file
al set clients claude,codex # Set CLI clients for the project
al add skill https://github.com/anthropics/skills/tree/main/skills/frontend-design # Add a skill
al sync # Sync skills and agents as per the lockfile
This will make an entry in AGENTS.lock and sync the skill to the appropriate locations for the specified clients. From that point, it is not necessary to manually manage the skills across different clients, but simply maintain a single AGENTS.lock file and run al sync to keep everything up to date.
Currently supported clients and features:
| Client | AGENTS.md | Skills | MCP |
|---|---|---|---|
| Claude | ✓ | ✓ | ✓ |
| Codex | ✓ | ✓ | ✗ |
| Copilot | ✓ | ✓ | ✗ |
| Gemini | ✓ | ✓ | ✗ |
Lockfile basics
AGENTS.lock is a TOML file that records project metadata, default clients, and the full set of
configured resources. Each entry carries a source, which can be a pinned git revision, a path
relative to the lockfile, or inline content for instructions. Groups provide a way to filter
subsets of resources during sync so teams can target specific workflows.
Install to project or global scope
Project scope writes within the repository. Global scope writes to user-level configuration paths.
al sync
al --global sync
Use lockfile aliases (alias file workflows)
If you manage multiple lockfiles, create an alias and target it via --lockfile.
al alias add work /path/to/AGENTS.lock
al --lockfile work sync
Metadata
Release files for agentslock 0.0.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 | Provenance | Actions |
|---|---|---|---|---|
| agentslock-0.0.1.tar.gz | 39.5 kB | Without provenance | Details for agentslock-0.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| agentslock-0.0.1-py3-none-any.whl | Python 3 | none | any | Details for agentslock-0.0.1-py3-none-any.whl |
Total release size: 85.9 kB
Release files / agentslock-0.0.1.tar.gz
| Download URL | agentslock-0.0.1.tar.gz |
|---|---|
| Size | 39.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b10b90d4ef623db7ae14880a7c6f5c23e64329cdd75ecebde35cd6894ba966ca
|
|
BLAKE2b-256 checksum How to use checksums |
7b9bc98b07812d01c3c8299afd0af329f2852b096f1c1d25c1e19dd1f68204af
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.8
|
Release files / agentslock-0.0.1-py3-none-any.whl
| Download URL | agentslock-0.0.1-py3-none-any.whl |
|---|---|
| Size | 46.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
eacf39a8c0fd3b187165dea6aa3fb72b4ce05999173102fb9192ca918b0534fa
|
|
BLAKE2b-256 checksum How to use checksums |
f9fc7f1f1ab88d1cd1b91024ec3dda2f89b7dc84b68d00cc96d153f658a3304a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.8
|
Security for agentslock 0.0.1
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.