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.
npx agentmods add instructions/mariotaddeucci/template-mcp/copilot-instructionsgit clone --depth 1 https://github.com/mariotaddeucci/template-mcpWrote 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.
[](https://agentmods.dev/instructions/mariotaddeucci/template-mcp/copilot-instructions)<a href="https://agentmods.dev/instructions/mariotaddeucci/template-mcp/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/mariotaddeucci/template-mcp/copilot-instructions.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.01021 | $0.01021 |
| Opus 5 | $0.00511 | $0.00511 |
| Sonnet 5 | $0.00204 | $0.00204 |
| Haiku 4.5 | $0.00102 | $0.00102 |
Grade A, and why
template-mcp 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.
How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Copilot Instructions
Project Overview
This project is a secure MCP (Model Context Protocol) server using FastMCP and Eunomia Authorization. It will become public, so follow security and documentation best practices.
Package Management
- Use uv: Use
uvas the package manager for all Python dependencies and tool installations - Python Version: Requires Python >= 3.12 as specified in pyproject.toml
- Ruff: Use Ruff as the official formatter and linter for code quality and consistency
- Taskipy: Use Taskipy with uv for task automation via
uv run task <task-name>
Development Tools
Code Quality
- Ruff as Formatter: Use
uv run ruff formatto format code according to project standards - Ruff as Linter: Use
uv run ruff checkto lint code and catch potential issues - Pre-commit integration: Ruff should be configured to run before commits for consistent code quality
Task Automation
- Taskipy integration: Use Taskipy for common development tasks
- Task execution: Run tasks using
uv run task <task-name>format - Common tasks: Examples include
uv run task lint,uv run task format,uv run task test - Custom tasks: Define project-specific tasks in pyproject.toml under
[tool.taskipy.tasks]
Workflow and Task Management
Pre-Task Checklist
Before starting tasks:
- Check for existing approved PRs related to your intended work
- Review open issues to avoid duplication of effort
- If approved PRs exist, perform squash merge using GitHub MCP tools
- Update local branch with latest changes from main branch
Task Execution Rules
- One task at a time: Execute only one task at a time
- Complete verification: Ensure all steps are successfully completed before marking task as done
- Use GitHub MCP: Utilize GitHub MCP tools for opening issues and pull requests
Git Workflow
Branch Management
- Never commit directly to main/master: Always create separate branches for features or fixes
- Branch naming: Use descriptive branch names (e.g.,
feat/setup-mcp-server,fix/auth-middleware) - Pull requests required: All changes must go through PR review process
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.
- 5d ago First seen · 102 lines · 1,021 tokens per session scan A 1b01a41b6e4c
template-mcp copilot-instructions.md is an instructions file published in the GitHub repository mariotaddeucci/template-mcp (0 stars, last pushed 1y ago), licensed MIT. It adds 1,021 tokens to every session, about $0.0051 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-31.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).