agentmods.dev

mcp-linear: Instructions file for GitHub Copilot

.github/copilot-instructions.md

mcp-linear copilot-instructions.md is an instructions file for GitHub Copilot from tacticlaunch/mcp-linear. It costs 517 tokens per session, scanned A, original, MIT.

Repository instructions for an MCP server that connects coding agents to Linear, a project-management and issue-tracking service.

In plain words
What is it for?
Use them when adding, changing, or reviewing Linear-facing tools, services, handlers, schemas, or related tests.
Why use it?
They show where Linear integration code belongs and how to change tools while preserving validation, error handling, and tests.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file.

This is tacticlaunch/mcp-linear's own configuration. It tells GitHub Copilot how to work on mcp-linear 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 mcp-linear configures →

not rated 148repo 17d ago A scan 517 tokens original MIT
View source ↗ tacticlaunch/mcp-linear
Reuse

Borrowing it

Nothing to install: this file belongs to tacticlaunch/mcp-linear. 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/tacticlaunch/mcp-linear/main/.github/copilot-instructions.md
Clone the repo
git clone --depth 1 https://github.com/tacticlaunch/mcp-linear

Made for: GitHub Copilot.

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 mcp-linear copilot-instructions.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/tacticlaunch/mcp-linear/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/tacticlaunch/mcp-linear/copilot-instructions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 517 This file is loaded in full into every session.
When invoked 517 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.00517 $0.00517
Opus 5.5 $0.00207 $0.00207
Sonnet 5.5 $0.00103 $0.00103
Haiku 4.5 $0.00052 $0.00052

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

Security

Grade A, and why

mcp-linear copilot-instructions.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 2mo 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.

.github/copilot-instructions.md · 39 lines

How it starts

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

MCP Linear Repository Instructions

This repository is an MCP server for Linear, not an application. Most work in this repo adds, updates, or reviews Linear-facing MCP tools.

Repository Map

  • src/services/linear-service.ts: main integration layer for @linear/sdk and the place where MCP-facing response normalization should happen.
  • src/tools/definitions/*.ts: MCP tool definitions and input/output schemas, grouped by domain.
  • src/tools/handlers/*.ts: thin handlers that validate arguments, delegate to LinearService, and log errors.
  • src/tools/type-guards.ts: runtime validation for tool arguments.
  • src/tools/definitions/index.ts and src/tools/handlers/index.ts: central registration.
  • src/__tests__/*.ts: focused Jest coverage for service behavior and tool wiring.
  • TOOLS.md: user-facing tool inventory and planned work.
  • package.json: package metadata.

How To Add Or Change A Tool

  • Start by checking whether the capability already exists in src/services/linear-service.ts.
  • Prefer @linear/sdk methods and generated types first.
  • Use direct GraphQL only when the SDK is missing support or ships a stale query. If you do this, keep the query narrow and document why.
  • Keep service methods responsible for returning normalized plain objects, not raw SDK entities.
  • Keep handlers thin.
  • Keep input_schema, output_schema, type guards, and normalized service output aligned exactly, especially around nullable fields and enums.
  • Register every new tool in both index files.
  • Update TOOLS.md when the public tool surface changes.

Validation

  • Always run npm test and npm run build before considering work complete.
  • Use npm run dev -- --token YOUR_LINEAR_API_TOKEN for local server development.
  • Use npm run inspect -- -e LINEAR_API_TOKEN=YOUR_LINEAR_API_TOKEN when validating the local MCP server with the inspector.

Project-Specific Pitfalls

  • This repo frequently needs careful SDK contract inspection. Check node_modules/@linear/sdk/dist/_generated_sdk.d.ts and _generated_documents.d.ts before guessing field names or mutation inputs.
  • Some Linear product naming does not match SDK naming. For example, saved views are CustomView in the API and SDK.
  • Review changes carefully for schema drift between service output, tool definitions, and type guards.
  • Keep changes minimal and domain-local. Prefer extending an existing domain file over introducing new structure unless the domain is clearly separate.

Read the full file on GitHub · 39 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. 2mo ago First seen · 39 lines · 517 tokens per session scan A 73e124580827

Subscribe to this mod's changes

mcp-linear copilot-instructions.md is an instructions file published in the GitHub repository tacticlaunch/mcp-linear (148 stars, last pushed 17d ago), licensed MIT. It adds 517 tokens to every session, about $0.0021 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.

Project managementclaudecursorlinearmcp
Related

Other instructions, from other repositories

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 · 9,715 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,461 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, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 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,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,750 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,261 tokens