Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/atomicstrata/atomicmemory-python/agents-mdgit clone --depth 1 https://github.com/atomicstrata/atomicmemory-pythonWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00778 | $0.00778 |
| Opus 5 | $0.00389 | $0.00389 |
| Sonnet 5 | $0.00156 | $0.00156 |
| Haiku 4.5 | $0.00078 | $0.00078 |
Grade A, and why
atomicmemory-python AGENTS.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
Copies of this mod
1 near-identical copy found in the catalogue:
- atomicmemory-python GEMINI.md — 100% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
atomicmemory-python — agent rules
Python client SDK for the AtomicMemory memory layer.
Contributor Context
Use this file as the repo-local contributor guide. When behavior depends on another AtomicMemory repo, rely on the published HTTP/package contract and call out any assumption in the PR.
Before changing code, read the relevant local files first:
README.mdfor user-facing installation and usage.pyproject.tomlfor supported Python versions, dependencies, and tool config.atomicmemory/for package code andtests/for expected behavior.
Repository Shape
atomicmemory/— typed Python package.tests/— unit and integration tests.examples/— public usage examples.pyproject.toml— package metadata and tool configuration.
Tooling
- Package management:
uv sync(NOTuv pip install). - Python interpreter:
.venv/bin/python. Never the globalpython. - HTTP:
httpx(syncClient, asyncAsyncClient). - Validation:
pydantic>=2.7.jsonschemaonly when validating against external JSON schemas. - Lint/format:
ruff(line=120).ruff format --check .is part of pre-commit. - Types:
mypy --strict. - Dead code / static health:
vulture --min-confidence 90. The whitelist file.vulture_whitelist.pyMUST be included in every invocation (it allowlists Protocol-method parameter names and context-manager dunder args). Use the[tool.vulture]config (uv run vulture) or pass it explicitly:uv run vulture atomicmemory tests .vulture_whitelist.py --min-confidence 90.fallowis TypeScript-only and is not part of this repo's verification. - Tests:
pytest,pytest-asyncio,pytest-mock,respx. Integration tests gated behind-m integration.
Code rules
- File ≤400 lines (excl. comments/docstrings); function ≤40 lines (excl. catch/finally and docstrings); test files ≤400 lines; tests ≤40 lines.
- Google-style docstrings (
Args:,Returns:,Raises:). - Module docstring at the top of every file. For modules that port a specific TS file, include the TS source-of-truth path (
"""Port of atomicmemory-sdk/src/.../foo.ts."""). - No fallback values; no
os.getenvin business code (config flows through Pydantic models constructed at startup). - No silent
except. No bareexcept:. - Greenfield code — no backwards-compat hacks, no
_private renames for "removed" code. - Snake_case for Python attributes; Pydantic
Field(alias="apiUrl")aliases preserve TS camelCase wire format. - Keep public API behavior aligned with
atomicmemory-sdkwhere both SDKs expose the same concept. - Prefer integration tests with a real HTTP path for client behavior; use mocks only for narrow transport errors.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- yesterday First seen · 66 lines · 778 tokens per session scan A 5212198e0e18
atomicmemory-python AGENTS.md is an instructions file published in the GitHub repository atomicstrata/atomicmemory-python (11 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 778 tokens to every session, about $0.0039 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
hindsight CLAUDE.md
Instructions for vectorize-io/hindsight, covering claude.md, project overview, development commands, local development (api + ui) and start both api server and control plane ui.
plur CLAUDE.md
Instructions for plur-ai/plur, covering claude.md, what is plur, development, package dependency and version bumps.
dense-mem AGENTS.md
Instructions for markhuangai/dense-mem, covering dense-mem repository guidance, project context, architecture decision records, current stack and target architecture.
pos CLAUDE.md
Instructions for xcota/pos, covering personal os, rules, memory, budget and hard rules.
mem9 AGENTS.md
Instructions for unvulcanised-watercress762/mem9, covering what this repo is, high-level modules, commands, go server build / verify and single go test.
agent-knowledge-cards AGENTS.md
Instructions for manojbajaj95/agent-knowledge-cards, covering agents.md, layout, on-disk cards, commands and rules.