mcpx AGENTS.md

Repository instructions for the mcpx project. They point agents to its skills, GitHub issue-tracking rules, triage labels, domain documentation, and architecture decisions.

In plain words
What is it for?
Use them when working on mcpx to find the required context, issue procedures, labels, and relevant architecture documents.
Why use it?
They give an agent the project context needed to handle issues consistently and understand the codebase.

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

Made for: Codex, OpenCode.

Per session 101 This file is loaded in full into every session.
When invoked 101 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.00101 $0.00101
Opus 5 $0.00051 $0.00051
Sonnet 5 $0.00020 $0.00020
Haiku 4.5 $0.00010 $0.00010

Measured 2d ago against content hash b968b286a4e5, 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 · 16 lines

What it actually says

Agent instructions

Agent skills

Issue tracker

Issues and build specifications are tracked in GitHub Issues for celados/mcpx. See docs/agents/issue-tracker.md.

Triage labels

Use the canonical triage labels defined in docs/agents/triage-labels.md.

Domain docs

This is a single-context repository. Read CONTEXT.md and relevant ADRs under docs/adr/. See docs/agents/domain.md.

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 · 16 lines · 101 tokens per session scan A b968b286a4e5

Subscribe to this mod's changes

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

Related

Other instructions, from other repositories