Borrowing it
Nothing to install: this file belongs to Daghis/teamcity-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.
curl -O https://raw.githubusercontent.com/Daghis/teamcity-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/Daghis/teamcity-mcpWrote 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.
[](https://agentmods.dev/instructions/daghis/teamcity-mcp/agents-md)<a href="https://agentmods.dev/instructions/daghis/teamcity-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/daghis/teamcity-mcp/agents-md.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.02071 | $0.02071 |
| Opus 5 | $0.01035 | $0.01035 |
| Sonnet 5 | $0.00414 | $0.00414 |
| Haiku 4.5 | $0.00207 | $0.00207 |
Grade A, and why
teamcity-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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
src/— TypeScript source. Key areas:teamcity/(API + managers),tools.ts(MCP tools),utils/,types/,config/,server.ts.tests/— Jest tests (unit/integration) plus mocks and setup.docs/— Additional docs; seeARCHITECTURE.mdfor design notes.scripts/— Build/tooling scripts. Build output goes todist/.- Path aliases:
@/utils,@/types,@/config,@/server,@/tools.
Build, Test, and Development Commands
npm run dev— Watch + runsrc/index.tsvia tsx.npm run build— Production build todist/.npm start— Run built server fromdist/.npm test|npm run test:unit|npm run test:integration— Run Jest suites.npm run test:coverage— Coverage report (thresholds enforced).npm run lint/npm run lint:check— ESLint with Prettier integration.npm run format— Format;npm run typecheck— TS type checking.- Node 20.x required. Use
.nvmrc(20.x). Copy.envfrom.env.exampleand fill values.
Coding Style & Naming Conventions
- Prettier: 2 spaces, 100 cols, single quotes, trailing commas; import order via
@trivago/prettier-plugin-sort-imports. - ESLint:
no-console— useutils/logger.ts(Winston). Prefer arrow functions,const, template strings. - Naming: types/interfaces/enums — PascalCase; vars/functions/params — camelCase; constants may be UPPER_CASE.
- Types: no
any; use generics/unknown/precise types. Public APIs have explicit return types. Default or named exports allowed.
Testing Guidelines
- Framework: Jest + ts-jest. Tests in
src/**/*.test.tsortests/**. Setup:jest.setup.js,tests/setup.ts; mocks intests/__mocks__/. - Coverage: ≥ 80% (branches, functions, lines, statements) via
npm run test:coverage. - Behavior-first: assert outputs, events, and side effects. Avoid peeking into internals or mock call counts except for thin adapters or explicit logging/redaction utilities.
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.
- 6d ago First seen · 130 lines · 2,071 tokens per session scan A 55fb90866cc6
teamcity-mcp AGENTS.md is an instructions file published in the GitHub repository Daghis/teamcity-mcp (28 stars, last pushed 5d ago), licensed MIT. It adds 2,071 tokens to every session, about $0.0104 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.
Other instructions, from other repositories
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.
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.
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).
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).
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.
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.