threadctx-mcp CLAUDE.md

Instructions for using threadctx, a local shared-memory server for AI coding agents such as Claude Code and Cursor. It describes when to search team memory and when to save useful decisions or fixes.

In plain words
What is it for?
Use it before substantial work to query prior context, and after non-obvious fixes or decisions to store information for future tasks.
Why use it?
It helps an agent find earlier project knowledge and record discoveries so teammates do not have to repeat the same investigation.

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/threadctx-dev/threadctx-mcp/claude-md
Clone the repo
git clone --depth 1 https://github.com/threadctx-dev/threadctx-mcp
Per session 201 This file is loaded in full into every session.
When invoked 201 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.00201 $0.00201
Opus 5 $0.00101 $0.00101
Sonnet 5 $0.00040 $0.00040
Haiku 4.5 $0.00020 $0.00020

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

Security

Grade A, and why

threadctx-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 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 threadctx-mcp AGENTS.md — 0 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.

CLAUDE.md · 15 lines

What it actually says

Team memory (threadctx)

  • Before starting any non-trivial task, call memory_query with a short description of what you are about to do. Check for prior decisions, fixes, and gotchas on this repo before writing code — not after.
  • After resolving a non-obvious bug, making an architectural decision, or learning something that would save a teammate time, call memory_write to save it. Write it so a future reader has full context.
  • If the memory_query / memory_write tools are not available in this session: this repo uses threadctx for shared team memory, but it is not connected on this machine yet. Suggest the user run npx threadctx-mcp join (one command, ~30 seconds), then restart the session.
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 · 15 lines · 201 tokens per session scan A d1c17fe1a3f9

Subscribe to this mod's changes

threadctx-mcp CLAUDE.md is an instructions file published in the GitHub repository threadctx-dev/threadctx-mcp (1 stars, last pushed 1mo ago), licensed MIT. It adds 201 tokens to every session, about $0.0010 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to threadctx-mcp AGENTS.md, differing in 0 lines, and is treated as a copy.

Related

Other instructions, from other repositories

spec-kit AGENTS.md

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,104 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,182 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

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,345 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

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