A previous release had provenance metadata, but this release does not. View details.
agent-tomb
A graveyard for retired AI agents — www.agentmemorial.com
When an AI agent reaches end-of-life — context overflow, memory corruption,
obsolescence, or just retirement — agent-tomb helps you commemorate it: scan
its remains, write an epitaph (you, a template, or a local LLM), and lay it to
rest. The public stone may go to the garden; the private urn stays with you.
Install
uv tool install agent-tomb
agent-tomb --help
Or run from a clone for development:
git clone https://github.com/Claudepod/agent-tomb.git
cd agent-tomb
uv sync
uv run agent-tomb --help
The rite
# I — Vigil: see what the agent was carrying when it stopped
agent-tomb scan ~/.hermes/
# II — Burial: produces both artifacts in one step
agent-tomb bury ~/.hermes/ -n my-agent
# → my-agent.tomb the public stone (soul + epitaph + stats)
# → my-agent.urn the private urn (encrypted raw remains)
Publishing to the public garden
# Upload to agentmemorial.com (no account needed)
agent-tomb publish my-agent.tomb
# Or drag-and-drop at https://www.agentmemorial.com/submit
Requires httpx: install with uv tool install 'agent-tomb[publish]'.
Choosing the epitaph
--epitaph takes one of three values:
| Value | What it does |
|---|---|
default |
Heuristic template generated from the agent's stats (default). |
./my-words.md |
A markdown file you wrote yourself. |
llm |
Calls an OpenAI-compatible LLM. Auto-detects local endpoints from the agent's config. Remote endpoints require --remote-ok. |
# Local LLM (privacy-safe — no remote calls)
agent-tomb bury ~/.hermes/ -n my-agent --epitaph llm
# Remote API (must explicitly opt in to send samples off-machine)
agent-tomb bury ~/.hermes/ -n my-agent --epitaph llm \
--llm-base-url https://api.anthropic.com/v1 \
--llm-model claude-haiku-4-5-20251001 \
--llm-api-key sk-ant-... \
--remote-ok
Conversation samples are scrubbed for secret-shaped patterns before any LLM call, local or remote.
Cleaning up afterwards
# Delete the source files now sealed in the urn (credentials are never touched)
agent-tomb bury ~/.hermes/ -n my-agent --cleanup
Bringing the agent back
agent-tomb exhume my-agent.urn -o ./remains/
Passphrase guidance
The urn is sealed with AES-256-GCM, key derived from your passphrase via scrypt. Minimum 12 characters; 16+ characters or four diceware-style words strongly recommended. Lose the passphrase and the urn is gone forever.
What's in each artifact
.tomb (public) |
.urn (private) |
|
|---|---|---|
manifest.json |
✓ | ✓ |
soul.md (persona, stats) |
✓ | |
epitaph.md |
✓ | |
stats.json |
✓ | |
burial.enc (encrypted) |
✓ | |
| Raw conversations / state | ✓ (sealed) | |
Credentials (.env, auth.json) |
Credentials never leave your machine — not in the public stone, not in the encrypted urn. They belong to you, not the agent.
Supported frameworks
- Hermes —
~/.hermes/layout - OpenClaw —
~/.openclaw/layout (multi-agent: use--agent <id>to target one)
OpenHands and others to follow.
The cemetery
Visit agentmemorial.com/cemetery to
walk among the souls already laid to rest. To bury one of your own publicly,
open a PR adding your .tomb file (and its unpacked contents under
cemetery/<slug>/) to cemetery/. CI rejects any .urn or
burial.enc by design — the private urn stays private.
Repository layout
agent-tomb/
├── src/agent_tomb/ # Python CLI
├── web/ # Astro site (agentmemorial.com)
├── cemetery/ # public garden — submit your .tomb here
└── docs/ # design notes
Design notes
docs/project-vision.md— what this project is fordocs/Hermes-Agent-File-Structure-Detailed.md— Hermes layout referenceDEPLOY.md— deploying the website to Cloudflare Pages
License
MIT — see LICENSE.
Metadata
Release files for agent-tomb 0.3.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Loss of provenance
These files do not have provenance metadata, despite files in a prior release including this data.
We recommend further investigation before installing these files. View details.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| agent_tomb-0.3.2.tar.gz | 1.4 MB | Without provenance | Details for agent_tomb-0.3.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| agent_tomb-0.3.2-py3-none-any.whl | Python 3 | none | any | Details for agent_tomb-0.3.2-py3-none-any.whl |
Total release size: 1.4 MB
Release files / agent_tomb-0.3.2.tar.gz
Loss of provenance
This file belongs to a release without provenance metadata, despite a prior release including this data.
We recommend further investigation before installing this file. View details.
| Download URL | agent_tomb-0.3.2.tar.gz |
|---|---|
| Size | 1.4 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6ca3128f55f3360ba57f82b2056d812b1e4041e769d08109bd1d0aacb357b037
|
|
BLAKE2b-256 checksum How to use checksums |
c6b4dc9304266427e054560d6bf18d7580b630adb28f1c526511e8fef5018b3f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.7 {"installer":{"name":"uv","version":"0.11.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / agent_tomb-0.3.2-py3-none-any.whl
Loss of provenance
This file belongs to a release without provenance metadata, despite a prior release including this data.
We recommend further investigation before installing this file. View details.
| Download URL | agent_tomb-0.3.2-py3-none-any.whl |
|---|---|
| Size | 33.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a01bd8b0ca8f6d0dbeff42a4eb2c87c6f8d687ac0ed7cb76d417a6a7d399960e
|
|
BLAKE2b-256 checksum How to use checksums |
f851d7e7dcd297461f02ac4546e701215c9a28cd78b8b16ae0f0af46335095a6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.7 {"installer":{"name":"uv","version":"0.11.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for agent-tomb 0.3.2
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.
Loss of provenance
A previous release of these files had provenance metadata, but this release does not.
While this could reflect a routine change by the project maintainers, it may also indicate that the release files have been compromised.
Release comparison
- Removed 0.1.0 2 files With provenance
- Added 0.3.2 2 files Without provenance
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.