mcpx AGENTS.md

Repository instructions for the mcpx project, covering its scope, working style, architecture boundaries, and checks for code changes. They also define the command structure for listing servers and calling their tools.

In plain words
What is it for?
Use them when changing mcpx code, especially its command-line interface, server and tool dispatch, daemon lifecycle, caching, or performance-sensitive paths.
Why use it?
They give contributors a shared set of rules for making small, reviewable changes while preserving the project’s command behaviour. They also specify tests and build checks that help catch regressions.

Instructions file for CodexOpenCode

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/lydakis/mcpx/agents-md
Clone the repo
git clone --depth 1 https://github.com/lydakis/mcpx

Made for: Codex, OpenCode.

Per session 540 This file is loaded in full into every session.
When invoked 540 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.00540 $0.00540
Opus 5 $0.00270 $0.00270
Sonnet 5 $0.00108 $0.00108
Haiku 4.5 $0.00054 $0.00054

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

Security

Grade A, and why

mcpx 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 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.

AGENTS.md · 52 lines

How it starts

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

AGENTS.md

Owner: George Lydakis (@lydakis)

Scope

  • This file applies to this repository.
  • Keep implementation aligned with docs/design.md.

Working Style

  • Keep diffs small and reviewable.
  • Favor root-cause fixes over patches.
  • For behavior changes and bug fixes, add/adjust tests first when practical.
  • Preserve the command contract unless intentionally changed:
    • mcpx lists servers
    • mcpx <server> lists tools
    • mcpx <server> <tool> calls tool
  • If repeated review rounds on the same subsystem keep surfacing new P1s, stop patching locally and write a short reset plan before continuing.

Quality Gates

  • Run go test ./... for changed scope.
  • Run go vet ./....
  • Run go build ./....
  • For performance-sensitive changes (daemon lifecycle, CLI dispatch, cache/pool hot paths), run make perf; use make perf-loop when validating warm CLI throughput.
  • Benchmark checks are manual/non-blocking unless explicitly requested as a hard gate; when run, include commands and a short before/after summary in handoff.
  • If any gate cannot run, document why in handoff.

Architecture Boundaries

  • internal/cli: CLI argument parsing and UX surface only.
  • internal/daemon + internal/ipc: lifecycle, socket auth, dispatch.
  • internal/mcppool: MCP transport/session concerns only.
  • internal/response: MCP result unwrapping/mapping only.
  • internal/cache: cache keying and TTL storage only.

Runtime And Cache Invariants

  • Preserve strict same-CWD correctness without adding synchronous config I/O to the unchanged warm path.
  • Runtime source monitoring and fingerprinting must observe the same files, including config, fallback, auth, OAuth credentials, and symlink targets.
  • Requested tool names control cache policy. Resolved backend tool identities control cache storage and validation.
  • Check cold-daemon and keepalive-expired behavior when strengthening cache or tool-validation invariants.
  • Cover unchanged and changed same-CWD requests, invalid config, cold-daemon cache hits, stale tools, and symlinked source edits with regressions.

Read the full file on GitHub · 52 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. 2d ago First seen · 52 lines · 540 tokens per session scan A d46ccb9d40f9

Subscribe to this mod's changes

mcpx AGENTS.md is an instructions file published in the GitHub repository lydakis/mcpx (52 stars, last pushed 3d ago), licensed MIT. It adds 540 tokens to every session, about $0.0027 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.