turbo_quant_memory: Instructions file for Claude Code

CLAUDE.md

turbo_quant_memory CLAUDE.md is an instructions file for Claude Code from Lexus2016/turbo_quant_memory. It costs 494 tokens per session, scanned A, original, MIT.

Project-specific instructions for Lexus2016/turbo_quant_memory, covering Claude Code, the tqmemory workflow, practical rules, and a secrets vault for phase 9.

In plain words
What is it for?
Guiding agent work on that repository, including tqmemory tasks and phase-9 secret handling.
Why use it?
It records the project rules an agent needs to follow, although the supplied description does not explain the workflow itself.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: mentions CLAUDE.md.

This is Lexus2016/turbo_quant_memory's own configuration. It tells Claude Code how to work on turbo_quant_memory itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything turbo_quant_memory configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Lexus2016/turbo_quant_memory. 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/Lexus2016/turbo_quant_memory/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/Lexus2016/turbo_quant_memory

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.

agentmods badge for turbo_quant_memory CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/lexus2016/turbo_quant_memory/claude-md/github.svg)](https://agentmods.dev/instructions/lexus2016/turbo_quant_memory/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/lexus2016/turbo_quant_memory/claude-md"><img src="https://agentmods.dev/badge/instructions/lexus2016/turbo_quant_memory/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.

agentmods 80×15 button for turbo_quant_memory CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/lexus2016/turbo_quant_memory/claude-md"><img src="https://agentmods.dev/badge/instructions/lexus2016/turbo_quant_memory/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 494 This file is loaded in full into every session.
When invoked 494 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00494 $0.00494
Opus 5.5 $0.00198 $0.00198
Sonnet 5.5 $0.00099 $0.00099
Haiku 4.5 $0.00049 $0.00049

Measured 1mo ago against content hash 9ae7147d14a5, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

turbo_quant_memory 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 1mo 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 · 26 lines

How it starts

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

CLAUDE.md

tqmemory Workflow

  • Treat tqmemory as always-available project memory for this repository.
  • Before editing an existing area, search project memory first.
  • Prefer compact retrieval first and use deeper hydration only when needed.
  • After important decisions, debugging outcomes, or handoffs, save one concise note.
  • After README, config, workflow, setup, or architecture changes, refresh indexed docs.
  • When old knowledge becomes stale, write the new note first and then deprecate the old note.
  • Promote to global memory only if the knowledge is reusable outside this repository.
  • Do not leave smoke or temporary notes active in memory.

Practical Rule

  • Use live project docs and current notes as the source of truth.
  • Treat .planning, .serena, and generated benchmark artifacts as historical context, not as the main operational contract.

Secrets Vault (Phase 9)

  • The vault is project-scoped and lives under ~/.turbo-quant-memory/projects/<project_id>/secrets/. Never index or search it.
  • Always discover the right get_secret(name) call from a pattern-kind recipe note via semantic_search. Do not guess names from chat history.
  • Pass secret_value through programmatically only — never echo into summaries, never store via remember_note.
  • If you encounter a master_key_unavailable or master_key_mismatch error response, surface its setup_hint verbatim to the user and stop; do not try to recover by guessing keys. master_key_mismatch (v0.11.0+) means the resolved key does not match the vault — usually a TQMEMORY_SECRETS_PASSPHRASE shadowing a keyring-keyed vault (the env var is an Argon2id passphrase, not the raw keyring key); the fix is normally to unset that env var. Reads never mint a new key, so the vault stays intact.
  • If the user already shared a credential in the chat (or you generated one inside the conversation), call set_secret(name, value) directly — you know the active project_id from cwd, the user running CLI from terminal may not. Recommend turbo-memory-mcp secret-set NAME from a terminal only as prevention (before the user pastes), not as remediation (after).

Read the full file on GitHub · 26 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. 1mo ago First seen · 26 lines · 494 tokens per session scan A 9ae7147d14a5

Subscribe to this mod's changes

turbo_quant_memory CLAUDE.md is an instructions file published in the GitHub repository Lexus2016/turbo_quant_memory (9 stars, last pushed 5d ago), licensed MIT. It adds 494 tokens to every session, about $0.0020 per session on Opus 5.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.

Related

Other instructions, from other repositories

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 · 9,715 tokens

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,461 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, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

langchain AGENTS.md

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

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,261 tokens