mcp-linear service.instructions.md

Repository instructions for using src/services/linear-service.ts as mcp-linear's single integration layer for Linear.

In plain words
What is it for?
Use it when implementing or modifying service methods that call Linear, normalize results, handle updates or clearing fields, or need direct GraphQL.
Why use it?
Keeping Linear API access in one service makes returned data more predictable and keeps handlers from duplicating integration logic. It also sets rules for nullable values, errors, and SDK fallbacks.

Instructions file for GitHub Copilot

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add instructions/tacticlaunch/mcp-linear/service
Clone the repo
git clone --depth 1 https://github.com/tacticlaunch/mcp-linear

Made for: GitHub Copilot.

Per session 167 This file is loaded in full into every session.
When invoked 167 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.00167 $0.00167
Opus 5 $0.00084 $0.00084
Sonnet 5 $0.00033 $0.00033
Haiku 4.5 $0.00017 $0.00017

Measured 2d ago against content hash a32fa5717f51, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

mcp-linear service.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 2d 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/service.instructions.md · 14 lines

What it actually says

This repository uses src/services/linear-service.ts as the single integration layer for Linear.

  • Prefer @linear/sdk methods and generated types before writing direct GraphQL.
  • If you must bypass the SDK, use this.client.client.request(...) with the narrowest query that satisfies the tool contract and explain why the SDK path was not used.
  • Normalize returned SDK entities into plain objects before returning them to handlers.
  • Keep response shapes honest about null, undefined, enums, and date handling.
  • Preserve explicit clearing semantics when the Linear API supports null for updates.
  • Throw precise errors that identify the entity or operation that failed.
  • Reuse helper functions for compacting inputs and handling nullable fields instead of open-coding one-off sanitization.
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. 2d ago First seen · 14 lines · 167 tokens per session scan A a32fa5717f51

Subscribe to this mod's changes

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