agentmods.dev

atomicmemory-python GEMINI.md

A repository guide for atomicmemory-python, a Python client library for the AtomicMemory memory service. It explains the project layout, development tools, and coding rules contributors should follow.

In plain words
What is it for?
It is for making and reviewing changes to the Python package, its tests, and its examples while following the repository's tooling and service-contract rules.
Why use it?
It tells coding agents which files to read, which Python environment and commands to use, and how to check formatting, types, and tests before changing the library.

Instructions file for Gemini CLI

11 2mo ago A scan 761 tokens copy · 100% Apache-2.0
View the source file atomicstrata/atomicmemory-python
Install

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.

agentmods
npx agentmods add instructions/atomicstrata/atomicmemory-python/gemini-md
Clone the repo
git clone --depth 1 https://github.com/atomicstrata/atomicmemory-python

Made for: Gemini CLI.

Per session 761 This file is loaded in full into every session.
When invoked 761 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

What 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.

ModelPer sessionOnce invoked
Fable 5 $0.00761 $0.00761
Opus 5 $0.00380 $0.00380
Sonnet 5 $0.00152 $0.00152
Haiku 4.5 $0.00076 $0.00076

Measured yesterday against content hash 54ae1cff80d9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

atomicmemory-python GEMINI.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.

Origin

This is a copy

100% identical to atomicmemory-python AGENTS.md — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

GEMINI.md · 66 lines

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.md for user-facing installation and usage.
  • pyproject.toml for supported Python versions, dependencies, and tool config.
  • atomicmemory/ for package code and tests/ 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 (NOT uv pip install).
  • Python interpreter: .venv/bin/python. Never the global python.
  • HTTP: httpx (sync Client, async AsyncClient).
  • Validation: pydantic>=2.7. jsonschema only 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.py MUST 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. fallow is 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.getenv in business code (config flows through Pydantic models constructed at startup).
  • No silent except. No bare except:.
  • 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-sdk where both SDKs expose the same concept.
  • Prefer integration tests with a real HTTP path for client behavior; use mocks only for narrow transport errors.

Read the full file on GitHub · 66 lines

Changes

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.

  1. yesterday First seen · 66 lines · 761 tokens per session scan A 54ae1cff80d9

Subscribe to this mod's changes

atomicmemory-python GEMINI.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 761 tokens to every session, about $0.0038 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to atomicmemory-python AGENTS.md, differing in 2 lines, and is treated as a copy.

Data and AIMemory and contextTestingagent-memoryagentsaiai-agentsai-memoryhttpx
Related

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.

vectorize-io/hindsight · 4,846 tokens

plur CLAUDE.md

Instructions for plur-ai/plur, covering claude.md, what is plur, development, package dependency and version bumps.

plur-ai/plur · 4,509 tokens

dense-mem AGENTS.md

Instructions for markhuangai/dense-mem, covering dense-mem repository guidance, project context, architecture decision records, current stack and target architecture.

markhuangai/dense-mem · 2,447 tokens

pos CLAUDE.md

Instructions for xcota/pos, covering personal os, rules, memory, budget and hard rules.

xcota/pos · 899 tokens

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.

unvulcanised-watercress762/mem9 · 1,827 tokens

agent-knowledge-cards AGENTS.md

Instructions for manojbajaj95/agent-knowledge-cards, covering agents.md, layout, on-disk cards, commands and rules.

manojbajaj95/agent-knowledge-cards · 861 tokens