microsoft-planner-mcp github-issues.instructions.md

A set of instructions for working with GitHub issues, which are tracked requests for bugs, features, or general tasks.

In plain words
What is it for?
Use it when creating, filing, triaging, or discussing an issue, and when deciding whether a question belongs in a GitHub Discussion instead.
Why use it?
It prevents issues from being filed in the wrong format or without required information.

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/aixolotl/microsoft-planner-mcp/github-issues
Clone the repo
git clone --depth 1 https://github.com/aixolotl/microsoft-planner-mcp

Made for: GitHub Copilot.

Per session 249 This file is loaded in full into every session.
When invoked 249 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.00249 $0.00249
Opus 5 $0.00125 $0.00125
Sonnet 5 $0.00050 $0.00050
Haiku 4.5 $0.00025 $0.00025

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

Security

Grade A, and why

microsoft-planner-mcp github-issues.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/github-issues.instructions.md · 24 lines

What it actually says

GitHub Issues

Always use the repository's issue templates when creating issues. Blank issues are disabled.

Available Templates

Template When to Use Title Prefix
Bug Report (bug.yml) Reporting a problem or unexpected behavior [Bug]
Feature Request (feature.yml) Proposing a new feature or enhancement [Feature]
Task (task.yml) General work items or activities [Task]

Questions that are not bugs, features, or tasks should be directed to GitHub Discussions.

Rules

  • Never create blank issues — always select the appropriate template
  • Always include the correct title prefix ([Bug] , [Feature] , or [Task] )
  • Fill in all required fields; do not leave template sections empty
  • If an issue does not fit any template, open a Discussion instead
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 · 24 lines · 249 tokens per session scan A 31ab712f8f8b

Subscribe to this mod's changes

microsoft-planner-mcp github-issues.instructions.md is an instructions file published in the GitHub repository aixolotl/microsoft-planner-mcp (11 stars, last pushed 2mo ago), licensed MIT. It adds 249 tokens to every session, about $0.0012 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.