yandex-tracker-mcp: Instructions file for Codex

AGENTS.md

yandex-tracker-mcp AGENTS.md is an instructions file for Codex, OpenCode from aikts/yandex-tracker-mcp. It costs 4,751 tokens per session, scanned A, original, Apache-2.0.

Instructions for an MCP server that connects AI assistants to the Yandex Tracker API, a service for managing issues and project work. It describes the server's commands, API layers, and optional Redis caching.

In plain words
What is it for?
Use it to run, format, type-check, and test the server, or to change its issue, queue, user, template, and other Tracker integrations.
Why use it?
It gives contributors the required checks and shows where requests, API contracts, and cached data are handled.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions Claude Code; mentions AGENTS.md.

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

Reuse

Borrowing it

Nothing to install: this file belongs to aikts/yandex-tracker-mcp. 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/aikts/yandex-tracker-mcp/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/aikts/yandex-tracker-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 yandex-tracker-mcp AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/aikts/yandex-tracker-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/aikts/yandex-tracker-mcp/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 4,751 This file is loaded in full into every session.
When invoked 4,751 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.04751 $0.04751
Opus 5.5 $0.01900 $0.01900
Sonnet 5.5 $0.00950 $0.00950
Haiku 4.5 $0.00475 $0.00475

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

Security

Grade A, and why

yandex-tracker-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 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 · 192 lines

How it starts

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

AGENTS.md

This file provides guidance to AI coding agents (Claude Code, Cursor, etc.) when working with code in this repository.

Rules

Before naming a tool, writing a description, a CHANGELOG entry or a README section, read the rule that covers it - rules/README.md indexes them, and each names the test that enforces it. This file covers the rest: architecture, the Tracker API's behaviour, and how to test.

Project Overview

MCP Yandex Tracker is a Model Context Protocol (MCP) server that provides tools for interacting with Yandex Tracker API. It implements a FastMCP server with protocol-based architecture and optional Redis caching.

Commands

task              # Run all checks (format, lint, type checking, tests) - REQUIRED before commits
task format       # Auto-format code
task check        # Run type and format checking
task test         # Run tests
uv sync           # Install dependencies
uv run mcp-tracker # Run the server

Architecture

  • Protocols (mcp_tracker/tracker/proto/): Define API contracts (QueuesProtocol, IssueProtocol, GlobalDataProtocol, TemplatesProtocol, UsersProtocol, EntitiesProtocol, BoardsProtocol, ComponentsProtocol), each exposed on AppContext as queues / issues / fields / templates / users / entities / boards / components
  • Client (mcp_tracker/tracker/custom/client.py): Implements protocols, handles HTTP requests
  • Caching (mcp_tracker/tracker/caching/client.py): Wraps protocols with Redis caching
  • MCP Server (mcp_tracker/mcp/server.py): Server creation and configuration
  • MCP Tools (mcp_tracker/mcp/tools/): Tool definitions organized by category
    • _access.py: Access control helpers (check_issue_access, check_queue_access)
    • queue.py / queue_write.py: Queue read-only / write tools
    • field.py: Global field and metadata tools (read-only)
    • template.py: Issue and comment template tools (read-only)
    • board.py: Board and sprint tools (read-only)
    • component.py / component_write.py: Queue component read-only / write tools (queue_get_components itself lives with the queue tools)
    • issue_read.py / issue_write.py: Issue read-only / write tools
    • user.py: User tools (read-only)
    • __init__.py: Exports register_all_tools() which orchestrates tool registration
    • *_write.py modules are only registered when settings.tracker_read_only=False
    • project/portfolio/goal modules are only registered when settings.tracker_entities_enabled=True
  • Settings (mcp_tracker/settings.py): Pydantic settings from environment variables
  • All protocol methods accept optional auth: YandexAuth | None parameter for OAuth support.
  • All Pydantic models for Yandex Tracker entities inherit from BaseTrackerEntity.

Read the full file on GitHub · 192 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 Changed · +5 lines · +881 tokens per session addd575b861f
  2. 1mo ago Changed · +6 lines · +710 tokens per session 994e8d68dfb3
  3. 1mo ago First seen · 181 lines · 3,160 tokens per session scan A 161bebc5729a

Subscribe to this mod's changes

yandex-tracker-mcp AGENTS.md is an instructions file published in the GitHub repository aikts/yandex-tracker-mcp (123 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 4,751 tokens to every session, about $0.0190 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