change-trace-mcp AGENTS.md

change-trace-mcp AGENTS.md is an instructions file for Codex, OpenCode from Canlendula/change-trace-mcp. It costs 705 tokens per session, scanned A, original, Apache-2.0.

Repository instructions define how coding agents share work in a project. They assign one coordinator to review and release changes, while other agents work only on assigned tasks.

In plain words
What is it for?
Use them to set rules for agent roles, task files, allowed files, acceptance checks, handoffs, merges, and releases in a shared repository.
Why use it?
They prevent multiple agents from changing project decisions, releases, or shared files without authority. They also make worker tasks and handoffs easier to review.

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/canlendula/change-trace-mcp/agents-md
Clone the repo
git clone --depth 1 https://github.com/Canlendula/change-trace-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 change-trace-mcp AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/canlendula/change-trace-mcp/agents-md.svg)](https://agentmods.dev/instructions/canlendula/change-trace-mcp/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/canlendula/change-trace-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/canlendula/change-trace-mcp/agents-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 705 This file is loaded in full into every session.
When invoked 705 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.1 $0.00705 $0.00705
Opus 5 $0.00352 $0.00352
Sonnet 5 $0.00141 $0.00141
Haiku 4.5 $0.00071 $0.00071

Measured 4d ago against content hash 3a9f5c3dc2b0, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

change-trace-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 4d 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 · 75 lines

How it starts

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

Repository Agent Rules

These rules apply to every Agent session working in this repository.

Role resolution

  • One user-designated primary session is the coordinator, reviewer, and release owner.
  • Every other session or sub-agent is an implementation worker unless its task assignment explicitly identifies it as the coordinator.
  • A worker cannot promote itself to coordinator or infer coordinator authority from access to the repository.

Coordinator-only authority

Only the coordinator may:

  • modify docs/ROADMAP.md, milestone status, exit-gate status, or the global backlog;
  • modify docs/PROJECT_DECISIONS.md;
  • modify this file, docs/CONTRIBUTING_WORKFLOW.md, or the work-item templates;
  • accept or reject a worker handoff;
  • merge or cherry-pick work into main;
  • change package versions, create tags or releases, publish npm packages, or change npm dist-tags;
  • publish compatibility claims or declare a milestone/release complete.

Workers may propose any of these changes in their work-item report.

Worker requirements

  • Work only from a task file under docs/work-items/ with a task ID, base commit, scope, allowed paths, acceptance criteria, and validation commands.
  • Use an isolated branch and worktree for any write task. The primary worktree and main belong to the coordinator.
  • Stay inside the assigned scope. Stop and report needs_decision when a public contract, dependency, security policy, or product decision must change beyond the assignment.
  • Do not modify coordinator-only files, merge into main, rebase shared branches, force-push, tag, publish, or perform release actions.
  • Update only the worker-owned handoff section of the assigned work-item file.
  • Commit implementation, tests, permitted documentation, and the handoff record to the task branch. Uncommitted changes are not handoff output.
  • Report task status as ready_for_review, blocked, or needs_decision. These states do not mean the milestone is complete.
  • Include exact validation commands and results, known limitations, deviations, and decision requests in the handoff.

Read the full file on GitHub · 75 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. 4d ago First seen · 75 lines · 705 tokens per session scan A 3a9f5c3dc2b0

Subscribe to this mod's changes

change-trace-mcp AGENTS.md is an instructions file published in the GitHub repository Canlendula/change-trace-mcp (0 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 705 tokens to every session, about $0.0035 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-31.

Related

Other instructions, from other repositories

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

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

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,296 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,469 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