phrase-mcp-server AGENTS.md

Repository instructions for a phrase MCP server, a service that exposes tools for agents through the Model Context Protocol.

In plain words
What is it for?
Use them when contributing to the repository, especially when naming tools, writing Conventional Commit messages, or registering tools with the required annotation fields.
Why use it?
They define checks that keep commits, pull-request titles, tool names, and tool safety annotations valid.

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

Made for: Codex, OpenCode.

Per session 1,037 This file is loaded in full into every session.
When invoked 1,037 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.01037 $0.01037
Opus 5 $0.00518 $0.00518
Sonnet 5 $0.00207 $0.00207
Haiku 4.5 $0.00104 $0.00104

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

Security

Grade A, and why

phrase-mcp-server 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 · 98 lines

How it starts

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

Agent Guidelines

Guidance for AI agents (Claude, Copilot, etc.) contributing to this repository.

Commit Messages and PR Titles

All commit messages and PR titles must follow Conventional Commits. This is enforced by CI on pull requests.

Format: <type>: <description>

Common types:

  • feat — new feature or capability
  • fix — bug fix
  • docs — documentation changes only
  • chore — maintenance, dependencies, config
  • refactor — code change that neither fixes a bug nor adds a feature
  • test — adding or updating tests

Examples:

feat: add readOnlyHint/destructiveHint annotations to all tools
fix: change download-target-file-async annotation to readOnlyHint
docs: add working examples section to README
chore: update Dependabot configuration

The PR title must also follow this format — the Semantic PR check will fail otherwise.

Tool Names

Tool names must be at most 64 characters. This is enforced by the Anthropic MCP Directory Policy and verified by the test suite.

Tool Annotations

Every tool registered with server.registerTool must declare an annotations field in its config object with three required fields. This is required for MCP directory submission.

Required annotation fields

  • title — a short human-readable label. Must be prefixed with [Strings], [TMS], [BQE], or [Connectors] to disambiguate between the Phrase products (e.g. both Strings and TMS have "Get Job", "List Projects", etc.).

  • readOnlyHint: true — the tool does not modify operational user data. Use for:

    • get_* / get-* — fetch a single resource
    • list_* / list-* — list resources
    • search_* / search-* — search/query
    • Async polling helpers (get_async_request, get_async_limits, list_pending_requests)
    • Async download triggers and file retrieval (download_target_file_async, download_target_file_by_async_request, create_locale_download) — these initiate or retrieve exports but do not modify user data
    • Branch comparison (compare_branch, get_branch_comparison) — read-only diff computation

Read the full file on GitHub · 98 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 · 98 lines · 1,037 tokens per session scan A 36d0c18994f4

Subscribe to this mod's changes

phrase-mcp-server AGENTS.md is an instructions file published in the GitHub repository phrase/phrase-mcp-server (13 stars, last pushed 20d ago), licensed MIT. It adds 1,037 tokens to every session, about $0.0052 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.