yandex-tracker-mcp: Instructions file for Claude Code

CLAUDE.md

yandex-tracker-mcp CLAUDE.md is an instructions file for Claude Code from APonkratov/yandex-tracker-mcp. It costs 1,535 tokens per session, scanned A, original, from a forked repository, Apache-2.0.

A set of instructions for developing the Yandex Tracker MCP server, a program that lets coding agents interact with Yandex Tracker through the Model Context Protocol. It documents the project, commands, architecture, caching, access control, and testing.

In plain words
What is it for?
Use it when modifying, testing, formatting, or reviewing the Yandex Tracker MCP server.
Why use it?
It gives an agent the repository-specific rules needed to understand the codebase and run the required checks before commits.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: mentions CLAUDE.md; mentions Claude Code.

This is APonkratov/yandex-tracker-mcp's own configuration. It tells Claude Code 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 APonkratov/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/APonkratov/yandex-tracker-mcp/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/APonkratov/yandex-tracker-mcp

Made for: Claude Code.

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 CLAUDE.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/aponkratov/yandex-tracker-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/aponkratov/yandex-tracker-mcp/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,535 This file is loaded in full into every session.
When invoked 1,535 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 fork From a forked repository.
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.01535 $0.01535
Opus 5 $0.00767 $0.00767
Sonnet 5 $0.00307 $0.00307
Haiku 4.5 $0.00153 $0.00153

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

Security

Grade A, and why

yandex-tracker-mcp CLAUDE.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 12d 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.

CLAUDE.md · 150 lines

How it starts

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

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

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 (IssueProtocol, QueuesProtocol, etc.)
  • 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)
    • 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
  • 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.

Testing

Rules

  • Use pytest with asyncio mode auto
  • Use aioresponses for HTTP mocking in TrackerClient tests and @tests/aioresponses_utils.py for capturing request/response pairs.
  • Use AsyncMock with spec= for protocol mocking in MCP tool tests
  • Always type-hint all parameters including fixtures
  • Never import inside functions - all imports at top of file
  • Never use loops for test cases - use @pytest.mark.parametrize
  • Use model_construct() for creating Pydantic model fixtures (skips validation)

Read the full file on GitHub · 150 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. 12d ago First seen · 150 lines · 1,535 tokens per session scan A cc7e655a163b

Subscribe to this mod's changes

yandex-tracker-mcp CLAUDE.md is an instructions file published in the GitHub repository APonkratov/yandex-tracker-mcp (1 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 1,535 tokens to every session, about $0.0077 per session on Opus 5. A static security scan graded it A with 0 findings. It comes from a forked repository.

Related

Other instructions, from other repositories

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,126 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

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,153 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

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