threadctx-mcp: Instructions file for Codex

AGENTS.md

threadctx-mcp AGENTS.md is an instructions file for Codex, OpenCode from threadctx-dev/threadctx-mcp. It costs 201 tokens per session, scanned A, original, MIT.

Repository instructions for using a local shared-memory service with AI coding agents. They require checking saved team context before substantial work and recording useful decisions or fixes afterward.

In plain words
What is it for?
Use them when working on the threadctx project with its memory tools. If those tools are unavailable, they point to the command for connecting the local service.
Why use it?
They help prevent repeated mistakes and keep coding agents aware of decisions already made in the project.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md.

This is threadctx-dev/threadctx-mcp's own configuration. It tells Codex and OpenCode how to work on threadctx-mcp 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 threadctx-mcp configures →

Reuse

Borrowing it

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

Made for: Codex, OpenCode.

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

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/threadctx-dev/threadctx-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/threadctx-dev/threadctx-mcp/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
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. 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.00201 $0.00201
Opus 5.5 $0.00080 $0.00080
Sonnet 5.5 $0.00040 $0.00040
Haiku 4.5 $0.00020 $0.00020

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

Security

Grade A, and why

threadctx-mcp AGENTS.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 2mo 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

AGENTS.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. 2mo ago First seen · 15 lines · 201 tokens per session scan A d1c17fe1a3f9

Subscribe to this mod's changes

threadctx-mcp AGENTS.md is an instructions file published in the GitHub repository threadctx-dev/threadctx-mcp (1 stars, last pushed 3mo ago), licensed MIT. It adds 201 tokens to every session, about $0.0008 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,719 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,516 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 · 3,048 tokens

generative-ai-for-beginners AGENTS.md

AGENTS.md instructions for microsoft/generative-ai-for-beginners, covering agents.md, project overview, setup commands, initial repository setup and clone the repository.

microsoft/generative-ai-for-beginners · 2,850 tokens