paiml-mcp-agent-toolkit: Instructions file for Codex

AGENTS.md

paiml-mcp-agent-toolkit AGENTS.md is an instructions file for Codex, OpenCode from paiml/paiml-mcp-agent-toolkit. It costs 599 tokens per session, scanned A, original, MIT.

Repository instructions for PMAT, a toolkit that creates AI coding context and checks code quality. It uses contracts, which are written rules checked during the build.

In plain words
What is it for?
Use them when changing PMAT, writing or updating contracts, and checking formatting, complexity, static-analysis, and test results.
Why use it?
They require agents to update the intended contract first and run the same quality checks used before changes are accepted.

Instructions file for CodexOpenCode

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

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

Reuse

Borrowing it

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

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 paiml-mcp-agent-toolkit AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/paiml/paiml-mcp-agent-toolkit/agents-md"><img src="https://agentmods.dev/badge/instructions/paiml/paiml-mcp-agent-toolkit/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 599 This file is loaded in full into every session.
When invoked 599 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.00599 $0.00599
Opus 5.5 $0.00240 $0.00240
Sonnet 5.5 $0.00120 $0.00120
Haiku 4.5 $0.00060 $0.00060

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

Security

Grade A, and why

paiml-mcp-agent-toolkit 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 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.

AGENTS.md · 46 lines

How it starts

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

Antigravity Global Rules for PMAT

Welcome to the paiml-mcp-agent-toolkit (PMAT) codebase! PMAT is a zero-config AI context generation and code quality toolkit.

Agent Guidelines

  • Use the PMAT CLI via the configured MCP Server for quality checks and analysis.
  • Follow the rules defined in .agents/rules/ for all operations.
  • Maintain test coverage above 95% (as detailed in the rules).
  • Adhere to the autonomous verify loop protocol for self-correction.

When making code changes, ensure that PMAT quality gates (via the pmat-quality-feedback.sh hook) pass. If it fails, fix the code according to the feedback!

Contract-first, and how it is enforced

PMAT is contract-first: a rule's behaviour is declared in contracts/*.yaml and bound to the code by #[provable_contracts_macros::contract(...)], so the contract is checked by the build rather than by review. Write or update the contract before the code it governs.

Run pmat verify before every commit. It runs the gate set CI enforces — format, complexity, satd, clippy, tests — fail-fast, so green here means green in CI. The pre-commit hook and pmat quality-gate both skip clippy and tests; pmat verify does not.

pmat comply check audits the 157 registered rules. Two of them are worth knowing before you touch a number in a config file:

  • CB-2101 (threshold coherence) — every scalar threshold in .pmat-metrics.toml must bind to a metric in .pmat-ratchet.toml. A limit that is breached at HEAD, or so far from the measurement that nothing could ever reach it, fails. An unbound threshold fails too: a number enforced by nothing reads as enforcement and enforces nothing.
  • CB-2102 (ratchet) — baselines may only improve. The gate does not read the number; it re-runs the command recorded beside it. A metric that cannot be measured FAILS, because "we could not measure it" must never be recorded as "it did not regress".

That last rule generalises, and it is the one to internalise: a measurement with no failing condition is indistinguishable from a correct one. Prefer the compiler over a text search whenever the question is "does this construct appear in shipped code" — pmat is a linter, so its own source contains as data every pattern it hunts, and grepping it for a defect marker returns its own detectors. Before trusting any new gate, apply the defect it targets and confirm it turns red, then restore and confirm it turns green again.

Read the full file on GitHub · 46 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 · 46 lines · 599 tokens per session scan A 5bc9fe6e5f33

Subscribe to this mod's changes

paiml-mcp-agent-toolkit AGENTS.md is an instructions file published in the GitHub repository paiml/paiml-mcp-agent-toolkit (167 stars, last pushed today), licensed MIT. It adds 599 tokens to every session, about $0.0024 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-30.

Related

Other instructions, from other repositories

runtm copilot-instructions.md

Copilot instructions for runtm-ai/runtm, covering runtm tool instructions, critical rules, structure, adding endpoints and app/api/v1/myendpoint.py.

runtm-ai/runtm · 297 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 · 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,581 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