mcp-linear tests.instructions.md

Repository instructions for writing focused tests for mcp-linear tools and services.

In plain words
What is it for?
Use them when adding tests for MCP tool surfaces, service methods, validation rules, explicit null clearing, filtering, or normalized responses.
Why use it?
They ensure new behavior is tested on both successful and invalid inputs, including nullable updates, enum and number constraints, normalization, and GraphQL fallback behavior.

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/tests
Clone the repo
git clone --depth 1 https://github.com/tacticlaunch/mcp-linear

Made for: GitHub Copilot.

Per session 143 This file is loaded in full into every session.
When invoked 143 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.00143 $0.00143
Opus 5 $0.00072 $0.00072
Sonnet 5 $0.00029 $0.00029
Haiku 4.5 $0.00014 $0.00014

Measured yesterday against content hash f922e892b719, 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 tests.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 yesterday.

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/tests.instructions.md · 13 lines

What it actually says

Tests in this repository should be focused and MCP-specific.

  • Add narrow tests around the behavior introduced by the change instead of broad snapshots.
  • Cover at least one positive path and one negative or validation path for new tool surfaces.
  • When a service method uses a direct GraphQL fallback, test the expected normalized shape and any filtering logic.
  • When update inputs support null clearing, add a test that preserves explicit null values.
  • When schemas or guards add constraints like enums or positive integers, add tests that reject invalid values.
  • Prefer mocking the smallest possible surface of the Linear client or LinearService dependency needed for the scenario.
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. yesterday First seen · 13 lines · 143 tokens per session scan A f922e892b719

Subscribe to this mod's changes

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