lamoom-python CLAUDE.md

Project instructions for LamoomAI's Python codebase, covering dependency installation, tests, formatting, type hints, naming, errors, logging, and documentation.

In plain words
What is it for?
They are for installing dependencies with Poetry, running pytest, formatting and linting code, checking types, and adding tested Python functionality.
Why use it?
They give the coding agent consistent rules for changing, testing, and checking the Python project.

Instructions file

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/lamoomai/lamoom-python/claude-md
Clone the repo
git clone --depth 1 https://github.com/LamoomAI/lamoom-python
Per session 307 This file is loaded in full into every session.
When invoked 307 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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.00307 $0.00307
Opus 5 $0.00153 $0.00153
Sonnet 5 $0.00061 $0.00061
Haiku 4.5 $0.00031 $0.00031

Measured 2d ago against content hash 34c30a58eeb0, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

lamoom-python CLAUDE.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 2d ago.

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.

CLAUDE.md · 34 lines

What it actually says

Lamoom Python Project Guide

Build/Test/Lint Commands

  • Install deps: poetry install
  • Run all tests: poetry run pytest --cache-clear -vv tests
  • Run specific test: poetry run pytest tests/path/to/test_file.py::test_function_name -v
  • Run with coverage: make test
  • Format code: make format (runs black, isort, flake8, mypy)
  • Individual formatting:
    • Black: make make-black
    • isort: make make-isort
    • Flake8: make flake8
    • Autopep8: make autopep8

Code Style Guidelines

  • Python 3.9+ compatible code
  • Type hints required for all functions and methods
  • Classes: PascalCase with descriptive names
  • Functions/Variables: snake_case
  • Constants: UPPERCASE_WITH_UNDERSCORES
  • Imports organization with isort:
    1. Standard library imports
    2. Third-party imports
    3. Local application imports
  • Error handling: Use specific exception types
  • Logging: Use the logging module with appropriate levels
  • Use dataclasses for structured data when applicable

Project Conventions

  • Use poetry for dependency management
  • Add tests for all new functionality
  • Maintain >80% test coverage (current min: 81%)
  • Follow pre-commit hooks guidelines
  • Document public APIs with docstrings
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. 2d ago First seen · 34 lines · 307 tokens per session scan A 34c30a58eeb0

Subscribe to this mod's changes

lamoom-python CLAUDE.md is an instructions file published in the GitHub repository LamoomAI/lamoom-python (97 stars, last pushed 1y ago), licensed Apache-2.0. It adds 307 tokens to every session, about $0.0015 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.

Related

Other instructions, from other repositories

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,182 tokens

buildNext

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

next.js AGENTS.md

Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

spec-kit AGENTS.md

Instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,040 tokens

langchain AGENTS.md

Instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,345 tokens