What is Pseudolife-MCP CLAUDE.md?

Project instructions for Pseudolife-MCP, a software project that includes stored data, database structure, caches, and indexes. They define the checklist for changes that are shipped to the main branch.

Use them when modifying behavior, data schemas, database definitions, derived indexes, or release documentation in Pseudolife-MCP.

They prevent releases from becoming inconsistent by requiring related version, documentation, changelog, and test updates to change together.

How Pseudogiant-xr/Pseudolife-MCP configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to Pseudogiant-xr/Pseudolife-MCP. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/Pseudogiant-xr/Pseudolife-MCP/master/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/Pseudogiant-xr/Pseudolife-MCP

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/pseudogiant-xr/pseudolife-mcp/claude-md/github.svg)](https://agentmods.dev/instructions/pseudogiant-xr/pseudolife-mcp/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/pseudogiant-xr/pseudolife-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/pseudogiant-xr/pseudolife-mcp/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/pseudogiant-xr/pseudolife-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/pseudogiant-xr/pseudolife-mcp/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 4,473 This file is loaded in full into every session.

When invoked 4,473 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.04473	$0.04473
Opus 5	$0.02237	$0.02237
Sonnet 5	$0.00895	$0.00895
Haiku 4.5	$0.00447	$0.00447

Measured 10d ago against content hash 9ab74a211df8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

Pseudolife-MCP 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 10d 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 · 301 lines

How it starts

The opening of the file, as written. The whole thing — 301 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Pseudolife-MCP — project conventions

Conventions that aren't derivable from a quick read of the code. Follow them exactly; they exist because each one was violated at least once.

Shipping checklist (any change that lands on master)

CHANGELOG.md entry under [Unreleased] — every behavior, schema, or perf change gets one, in the existing dated-subsection style. Docs-only and test-only changes are exempt.
Schema bumps touch seven places together: SCHEMA_META_VERSION in pseudolife_memory/storage/schema.py, the doc mentions (README capabilities table + the DSN row and version-history table in docs/guide/configuration.md — both pinned by tests/test_release_ux.py, the history table including gap detection), the version pin (the single CURRENT_SCHEMA literal in tests/test_schema_version.py — no per-version file, no >= relaxation pass; the ladder is gap-checked by test_release_ux.py and test_atlas_currency.py. Whatever behavior the bump adds gets a test beside its consumer, or a row in tests/test_schema_ddl_shape.py if it is pure DDL shape — never a new test_schema_vNN.py), a CHANGELOG mention of vNN (pinned by test_release_ux.py), and docs/atlas/atlas.json meta.schema (pinned by tests/test_atlas_currency.py — re-verify the affected storage cards, don't just renumber), the two assert meta[0] == NN literal pins in tests/test_migrate_embeddings.py, and python ops/gen_llms_txt.py after any doc edit (tests/test_llms_txt.py pins the generated llms-full.txt). The v30 bump found the last two the hard way.
Full suite before commit — HF_HUB_OFFLINE=1 python -m pytest tests/ with the bench Postgres up (127.0.0.1:5433); PG-backed tests skip silently without it, which is not a pass.
Deploy only via ops/update.ps1 (backup → rollback tag → daemon-only --no-deps rebuild → health). Never docker compose down -v — the bank volumes are external precisely so that this is survivable, but don't test it.
After deploy, verify live, not just /health: exercise the changed path through the daemon (an MCP call, a psql check of new DDL).

Read the full file on GitHub · 301 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.

10d ago First seen · 301 lines · 4,473 tokens per session scan A 9ab74a211df8

Subscribe to this mod's changes

Pseudolife-MCP CLAUDE.md is an instructions file published in the GitHub repository Pseudogiant-xr/Pseudolife-MCP (4 stars, last pushed today), licensed Apache-2.0. It adds 4,473 tokens to every session, about $0.0224 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-31.

Code review Memory and context Testing agent-memory claude long-term-memory mcp mcp-server

next.js AGENTS.md

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

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,153 tokens

vscode buildNext.instructions.md

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

Pseudolife-MCP: Instructions file for Claude Code