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/withinfocus/tba-mcp-server/claude-mdgit clone --depth 1 https://github.com/withinfocus/tba-mcp-serverWrote 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/withinfocus/tba-mcp-server/claude-md)<a href="https://agentmods.dev/instructions/withinfocus/tba-mcp-server/claude-md"><img src="https://agentmods.dev/badge/instructions/withinfocus/tba-mcp-server/claude-md.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.02463 | $0.02463 |
| Opus 5 | $0.01231 | $0.01231 |
| Sonnet 5 | $0.00493 | $0.00493 |
| Haiku 4.5 | $0.00246 | $0.00246 |
Grade A, and why
tba-mcp-server CLAUDE.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 — 335 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Instructions for TBA MCP Server
Model Context Protocol (MCP) server that provides access to The Blue Alliance API for FIRST Robotics Competition data.
Project Overview
- Language: TypeScript with Node.js
- Framework: Model Context Protocol SDK
- Package Manager: pnpm (version pinned in
packageManager; settings inpnpm-workspace.yaml) - Main Entry:
src/index.ts - Build Output:
dist/ - Transport: stdio for MCP communication
Project Structure
Source Code Architecture
The codebase is organized into separate modules for maintainability:
-
src/index.ts- Main server entry point- Initializes the MCP server
- Sets up request handlers for ListTools and CallTool
- Connects to stdio transport
- Handles error logging and process lifecycle
-
src/tools.ts- Tool definitions- Exports the
toolsarray containing all MCP tool definitions - Each tool has: name, description, and inputSchema (JSON Schema format)
- Tool definitions describe what parameters each tool accepts
- Exports the
-
src/handlers.ts- Tool execution handlers- Exports
handleToolCall(name, args)function - Contains a switch statement that routes tool calls to their implementations
- Each case: validates input, calls TBA API, validates response, returns formatted result
- Exports
-
src/schemas.ts- Zod validation schemas- Input validation schemas: TeamKeySchema, YearSchema, EventKeySchema
- API response schemas: TeamSchema, EventSchema, MatchSchema, etc.
- All schemas use Zod for runtime type validation
-
src/utils.ts- Utility functionslog()- MCP-aware logging functiongetApiKey()- Retrieves and validates TBA_API_KEY environment variablemakeApiRequest()- Makes HTTP requests to TBA API with proper headers
Test Architecture
Tests are organized to mirror the source structure:
tests/schemas.spec.ts- Unit tests for all Zod schemastests/utils.spec.ts- Unit tests for utility functionstests/integration/*.spec.ts- Playwright integration tests for MCP protocol compliance
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 · 335 lines · 2,463 tokens per session scan A 458804208025
tba-mcp-server CLAUDE.md is an instructions file published in the GitHub repository withinfocus/tba-mcp-server (1 stars, last pushed yesterday), licensed MIT. It adds 2,463 tokens to every session, about $0.0123 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.
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).
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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.