agentmods.dev

mcp-linear tool-definitions.instructions.md

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

146 4d ago A scan 211 tokens original MIT
View the source file tacticlaunch/mcp-linear
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/tool-definitions
Clone the repo
git clone --depth 1 https://github.com/tacticlaunch/mcp-linear

Made for: GitHub Copilot.

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. 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.00211 $0.00211
Opus 5 $0.00105 $0.00105
Sonnet 5 $0.00042 $0.00042
Haiku 4.5 $0.00021 $0.00021

Measured 2d ago against content hash 6c9db8606e61, 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 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 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/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. 2d 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 (146 stars, last pushed 4d ago), licensed MIT. It adds 211 tokens to every session, about $0.0011 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.

ProductivityWriting and docsclaudecursorlinearmcp
Related

Other instructions, from other repositories

awesome-copilot-id AGENTS.md

Instructions for GulajavaMinistudio/awesome-copilot-id, covering communication, explanation and documentation, markdown formatting, user communication style and workflow & methodology.

GulajavaMinistudio/awesome-copilot-id · 7,686 tokens

hiveshare CLAUDE.md

Instructions for KB-perByte/hiveshare, covering hiveshare — claude.md, repo layout, build & run, key env vars (server) and naming: hive vs memory.

KB-perByte/hiveshare · 1,301 tokens

llm-safe-haven CLAUDE.md

Instructions for pleasedodisturb/llm-safe-haven, covering llm safe haven, what this is, project structure, tdd — non-negotiable (adopted 2026-08-17) and the contract.

pleasedodisturb/llm-safe-haven · 1,322 tokens

kleosrules AGENTS.md

Instructions for kleosr/kleosrules, a project described as: Cursor harness pack: user rules, skills, Bash hooks, local HANDOFF memory. macOS, Linux, Windows (WSL).

kleosr/kleosrules · 417 tokens

coding-agent-safety-gate AGENTS.md

Instructions for ASER-ho/coding-agent-safety-gate, covering agents / 代理规则, 仓库类型 / repository type and ai 代理规则 / rules for ai coding agents.

ASER-ho/coding-agent-safety-gate · 589 tokens

yapcap CLAUDE.md

Claude Code instructions for TopiCsarno/yapcap, a project described as: Native COSMIC panel applet showing local usage limits for Codex, Claude Code, and Cursor.

TopiCsarno/yapcap · 3 tokens