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/jessica-writes-code/speechwire-mcp/copilot-instructionsgit clone --depth 1 https://github.com/jessica-writes-code/speechwire-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/jessica-writes-code/speechwire-mcp/copilot-instructions)<a href="https://agentmods.dev/instructions/jessica-writes-code/speechwire-mcp/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/jessica-writes-code/speechwire-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 | $0.01483 | $0.01483 |
| Opus 5 | $0.00741 | $0.00741 |
| Sonnet 5 | $0.00297 | $0.00297 |
| Haiku 4.5 | $0.00148 | $0.00148 |
Grade A, and why
speechwire-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 3d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot Instructions for SpeechWireMCP
Project Overview
SpeechWireMCP is a Model Context Protocol (MCP) server that gives AI assistants secure access to SpeechWire tournament judge data for speech-and-debate (forensics) competitions. It scrapes manage.speechwire.com behind an authenticated session and exposes structured data through MCP tools.
Tech Stack
- Python 3.11+ — use modern syntax (
X | Yunions,list[dict], etc.) - MCP SDK (
mcppackage,FastMCP) — tool registration via@mcp.tool() - requests — HTTP client with a stateful
requests.Sessionfor auth cookies - BeautifulSoup4 — HTML parsing of SpeechWire pages
- Hatchling — PEP 517 build backend
- pytest — testing
- ruff — linting (line-length 100, target py311)
Architecture
src/speechwire_mcp/
├── server.py # FastMCP server, tool definitions, lazy client init
├── client.py # SpeechWireClient (4-step auth), _fetch_and_parse helper
├── parsing_helpers.py # Shared BS4 utilities (make_soup, td_safe, extract_int_query_param)
├── judges/
│ ├── client.py # Judge data retrieval (list, contact, availability, school)
│ └── parsers.py # Judge HTML → structured data parsing
├── login/
│ ├── client.py # Account & tournament discovery after login
│ └── parsers.py # Account list & tournament list parsing
├── rooms/
│ ├── client.py # Room list, usage grid, count retrieval
│ └── parsers.py # Room HTML → structured data parsing
├── results/
│ ├── client.py # Tab sheet results retrieval
│ └── parsers.py # Results HTML → structured data parsing
├── schematics/
│ ├── client.py # Schematic event list & round schematic retrieval
│ └── parsers.py # Schematic HTML → structured data parsing
├── structure/
│ ├── client.py # Timeslot & grouping retrieval
│ └── parsers.py # Schedule/grouping HTML → structured data parsing
└── teams/
├── client.py # Team list, entries, hybrid entries retrieval
└── parsers.py # Team HTML → structured data parsing
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.
- 3d ago First seen · 128 lines · 1,483 tokens per session scan A c7fff4b8c331
speechwire-mcp copilot-instructions.md is an instructions file published in the GitHub repository jessica-writes-code/speechwire-mcp (0 stars, last pushed 25d ago), licensed MIT. It adds 1,483 tokens to every session, about $0.0074 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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.