linear-mcp-server-again copilot-instructions.md

linear-mcp-server-again copilot-instructions.md is an instructions file for GitHub Copilot from larryhudson/linear-mcp-server-again. It costs 494 tokens per session, scanned A, a copy of simple-notion-mcp-server copilot-instructions.md, MIT.

A set of project instructions for working with GitHub and Linear-style issue tracking. It defines how tasks, branches, commits, pull requests, testing, and status updates should be handled.

In plain words
What is it for?
Use it when contributing to a repository that requires issues for major work, pull requests for changes, user confirmation before commits, and synchronization with the remote branch.
Why use it?
It gives collaborators and coding agents a shared process for making changes traceable and reviewable. It also reduces the chance of committing untested work or losing work outside the issue workflow.

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/larryhudson/linear-mcp-server-again/copilot-instructions
Clone the repo
git clone --depth 1 https://github.com/larryhudson/linear-mcp-server-again

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

README.md
[![agentmods](https://agentmods.dev/badge/instructions/larryhudson/linear-mcp-server-again/copilot-instructions.svg)](https://agentmods.dev/instructions/larryhudson/linear-mcp-server-again/copilot-instructions)
Your own site
<a href="https://agentmods.dev/instructions/larryhudson/linear-mcp-server-again/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/larryhudson/linear-mcp-server-again/copilot-instructions.svg" alt="Measured on agentmods" height="20"></a>
Per session 494 This file is loaded in full into every session.
When invoked 494 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod 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.00494 $0.00494
Opus 5 $0.00247 $0.00247
Sonnet 5 $0.00099 $0.00099
Haiku 4.5 $0.00049 $0.00049

Measured 5d ago against content hash f7073d518ec3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

linear-mcp-server-again 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 5d 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.

Origin

This is a copy

100% identical to simple-notion-mcp-server copilot-instructions.md — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.github/copilot-instructions.md · 42 lines

How it starts

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

Project Collaboration Rules

You have access to GitHub tools to help automate and enforce these collaboration rules.

When starting a new task, make sure you are on the main branch and have the latest changes from origin.

Commit Workflow

  • Before committing any changes, test them with the user to ensure they are working and do not introduce new errors. Only commit after user confirmation.
  • Commit each major step as you go, before proceeding to the next step.
  • After each commit, always push to the remote branch to keep the remote in sync.

Issue-Driven Development Workflow

  1. All Major Tasks Require Issues

    • Every significant feature, bug fix, or change must have a corresponding GitHub issue.
    • Issues should be descriptive, outlining the problem, goal, or feature clearly.
  2. Work via Pull Requests

    • All code changes must be made in branches and submitted as pull requests (PRs).
    • Each PR must reference the relevant issue(s) it addresses (e.g., "Closes #issue-number").
    • PR titles and descriptions should clearly state the purpose and link to the issue.
  3. Blockers, Challenges, and Status Updates

    • Any blockers, questions, or status updates must be posted as comments on the relevant issue or pull request.
    • If you encounter a blocker or get stuck (e.g., persistent errors, unsolved configuration issues), document the issue as a comment on the relevant GitHub issue or PR, including a summary of what was tried and the current state.
    • Use comments to discuss implementation details, request clarification, or provide progress updates.
  4. Review and Merge Process

    • PRs should be reviewed before merging.
    • Only merge PRs after ensuring they address the issue and pass all checks.
  5. General Guidelines

    • Keep communication clear and concise.
    • Reference issues and PRs in all discussions for traceability.
    • Update or close issues as work progresses and is completed.

Automation/Assistant Workflow

Read the full file on GitHub · 42 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. 5d ago First seen · 42 lines · 494 tokens per session scan A f7073d518ec3

Subscribe to this mod's changes

linear-mcp-server-again copilot-instructions.md is an instructions file published in the GitHub repository larryhudson/linear-mcp-server-again (1 stars, last pushed 1y ago), licensed MIT. It adds 494 tokens to every session, about $0.0025 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to simple-notion-mcp-server copilot-instructions.md, differing in 0 lines, and is treated as a copy.