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/danwahlin/marvel-mcp/copilot-instructionsgit clone --depth 1 https://github.com/DanWahlin/marvel-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/danwahlin/marvel-mcp/copilot-instructions)<a href="https://agentmods.dev/instructions/danwahlin/marvel-mcp/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/danwahlin/marvel-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.00838 | $0.00838 |
| Opus 5 | $0.00419 | $0.00419 |
| Sonnet 5 | $0.00168 | $0.00168 |
| Haiku 4.5 | $0.00084 | $0.00084 |
Grade A, and why
marvel-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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Marvel MCP Server Development Guide
Project Overview
This is a Model Context Protocol (MCP) server that provides AI tools access to the Marvel Comics API. The server exposes 6 main tools for fetching Marvel characters and comics data through a standardized MCP interface.
Architecture
Core Components
- Entry Point:
src/index.ts- MCP server setup with stdio transport - Tools Registry:
src/tools/tools.ts- Centralized tool exports - HTTP Client:
src/utils.ts- Marvel API authentication and request handling - Schema Definitions:
src/tools/schemas.ts- Shared Zod schemas for Marvel API responses
Tool Pattern
Each tool follows a consistent structure in src/tools/{tool_name}/:
get_characters/
├── index.ts # Tool definition with handler
└── schemas.ts # Input validation schema
Tool implementation pattern:
export const get_characters = {
description: `Fetch Marvel characters with optional filters.`,
schema: GetCharactersSchema,
handler: async (args: any) => {
const argsParsed = GetCharactersSchema.parse(args);
const res = await httpRequest('/characters', serializeQueryParams(argsParsed));
return CharacterDataWrapperSchema.parse(res);
}
};
Development Workflows
Build and Test
npm run build # TypeScript compilation to dist/
npm run watch # Watch mode compilation
npm run dev # Build + watch with nodemon
npm run inspect # Test with MCP Inspector
Local Development
- Use
npm run inspectto test tools with MCP Inspector web interface - Environment variables loaded from
.envfile (copy from.env.template) - Server runs in stdio mode for MCP hosts or HTTP mode for direct testing
Adding New Tools
- Create tool directory:
src/tools/new_tool/ - Define input schema in
schemas.tsusing Zod - Implement tool in
index.tsfollowing the pattern above - Export from
src/tools/tools.ts - Update response schemas in
src/tools/schemas.tsif needed
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 · 114 lines · 838 tokens per session scan A 5c0e78bc3e45
marvel-mcp copilot-instructions.md is an instructions file published in the GitHub repository DanWahlin/marvel-mcp (14 stars, last pushed 9mo ago), licensed MIT. It adds 838 tokens to every session, about $0.0042 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.
Other instructions, from other repositories
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.
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.
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).