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/jimthompson5802/mcp_testlab/copilot-instructionsgit clone --depth 1 https://github.com/jimthompson5802/mcp_testlabWrote 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/jimthompson5802/mcp_testlab/copilot-instructions)<a href="https://agentmods.dev/instructions/jimthompson5802/mcp_testlab/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/jimthompson5802/mcp_testlab/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.00785 | $0.00785 |
| Opus 5 | $0.00392 | $0.00392 |
| Sonnet 5 | $0.00157 | $0.00157 |
| Haiku 4.5 | $0.00078 | $0.00078 |
Grade A, and why
mcp_testlab 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 4d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot Instructions
These instructions help GitHub Copilot understand how to assist with the MCP Testlab project.
Project Overview
This project demonstrates using the Model Context Protocol (MCP). It uses the FastMCP Python SDK to create tools that can be accessed via multiple transport protocols. The main focus is on a sentiment analysis tool that can analyze text and return sentiment scores.
- An MCP server FastMCP Server
- An MCP client FastMCP Client
- Multiple MCP clients using different transport protocols (stdio, SSE, streamable-http)
- Command-line interfaces to interact with the sentiment analysis tool
Coding Style
When contributing to this project, follow these coding style guidelines:
-
Python Style:
- Follow PEP 8 conventions for Python code
- Allow line length up to 120 characters
- Use PascalCase for class names (e.g.,
SentimentAnalyzer) - Use snake_case for variables and functions (e.g.,
analyze_text,sentiment_score)
-
Type Hints: Include type annotations for function parameters and return values
-
Documentation:
- Add docstrings to all functions and classes
- Use Google-style docstrings with Args and Returns sections
-
Error Handling:
- Use try/except blocks for error handling
- Provide descriptive error messages
-
Async Programming:
- Use asyncio for asynchronous operations
- Employ async context managers with AsyncExitStack for resource cleanup
-
Command-line Interfaces:
- Use argparse for processing command-line arguments
- Provide helpful descriptions for all arguments
-
Code Organization:
- Keep classes focused on a single responsibility
- Use clear, descriptive variable and function names
- Group related functionality within classes
-
LLM Prompt
- when a prompt will span muliple lines use the triple quotes
"""to enclose the prompt text. - use
textwrap.dedentto remove any common leading whitespace.
- when a prompt will span muliple lines use the triple quotes
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.
- 4d ago First seen · 95 lines · 785 tokens per session scan A bdd22f124b0a
mcp_testlab copilot-instructions.md is an instructions file published in the GitHub repository jimthompson5802/mcp_testlab (0 stars, last pushed 10mo ago), licensed MIT. It adds 785 tokens to every session, about $0.0039 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-09-01.
Other instructions, from other repositories
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.
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.
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).