mcp-linear: Instructions file for GitHub Copilot

.github/instructions/tool-definitions.instructions.md

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

Repository instructions for keeping mcp-linear tool definitions, handlers, and type guards aligned. A type guard is code that checks whether incoming data has the expected shape.

In plain words
What is it for?
Use them when changing MCP tools, including their input and output schemas, required fields, enums, nullable values, handlers, type guards, registrations, or documentation.
Why use it?
They reduce errors where documentation or schemas promise one thing but validation or handlers expect another. They also require consistent registration and honest output descriptions.

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 →

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/instructions/tool-definitions.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 tool-definitions.instructions.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/tacticlaunch/mcp-linear/tool-definitions"><img src="https://agentmods.dev/badge/instructions/tacticlaunch/mcp-linear/tool-definitions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 211 This file is loaded in full into every session.
When invoked 211 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.00211 $0.00211
Opus 5.5 $0.00084 $0.00084
Sonnet 5.5 $0.00042 $0.00042
Haiku 4.5 $0.00021 $0.00021

Measured 2mo ago against content hash 6c9db8606e61, 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 tool-definitions.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/instructions/tool-definitions.instructions.md · 14 lines

What it actually says

Changes in the MCP surface must keep definitions, handlers, and guards aligned.

  • input_schema, type guards, and handler expectations must use the same field names and required fields.
  • output_schema must match the actual normalized service output, including nullable objects, nullable strings, enums, and numeric constraints.
  • Prefer explicit enums and positive integer constraints over generic string or number schemas when the contract is known.
  • Handlers in this repo should stay thin: validate, delegate to LinearService, and log failures.
  • Every new public tool must be registered in both src/tools/definitions/index.ts and src/tools/handlers/index.ts.
  • If the tool is intended for external clients, update TOOLS.md in the same change.
  • Call out API naming mismatches directly in descriptions when needed, such as Linear saved views being exposed as CustomView in the SDK.
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 · 14 lines · 211 tokens per session scan A 6c9db8606e61

Subscribe to this mod's changes

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

data-scientist copilot-instructions.md

Repository instructions for a data-science workflow in GitHub Copilot, covering datasets, statistics, and analysis files.

realnghon/data-scientist · 373 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 · 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