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/mrgoonie/vidcap-mcp-server/agents-mdgit clone --depth 1 https://github.com/mrgoonie/vidcap-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/mrgoonie/vidcap-mcp-server/agents-md)<a href="https://agentmods.dev/instructions/mrgoonie/vidcap-mcp-server/agents-md"><img src="https://agentmods.dev/badge/instructions/mrgoonie/vidcap-mcp-server/agents-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.1 | $0.00316 | $0.00316 |
| Opus 5 | $0.00158 | $0.00158 |
| Sonnet 5 | $0.00063 | $0.00063 |
| Haiku 4.5 | $0.00032 | $0.00032 |
Grade A, and why
vidcap-mcp-server AGENTS.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.
Copies of this mod
1 near-identical copy found in the catalogue:
- vidcap-mcp-server CLAUDE.md — 100% identical, 0 lines differ
What it actually says
VidCap MCP Server - Agent Instructions
Build & Development Commands
- Build:
npm run build(TypeScript to CommonJS) - Lint:
npm run lint(ESLint with Prettier) - Format:
npm run format(Prettier auto-format) - Test:
npm run test(Jest with no-tests-pass) - Test Coverage:
npm run test:coverage - Dev Server:
npm run dev:server(builds & starts with DEBUG=true)
Code Style & Conventions
- Indentation: Tabs (4-space width), SwitchCase: 1 level
- Quotes: Single quotes, semicolons required, trailing commas
- Imports: Use
.jsextensions for imports (ESM syntax, CommonJS output) - Naming: camelCase for variables/functions, PascalCase for types/classes
- Types: Strict TypeScript, Zod schemas for validation, explicit return types
- Error Handling: Try-catch blocks, proper error logging with contextual loggers
- Logging: Use
Logger.forContext('filename', 'method')pattern - Comments: JSDoc for public APIs, minimal inline comments
Project Structure
- MCP server with YouTube API integration using VidCap
- TypeScript source in
src/, CommonJS output indist/ - Zod schemas in
types/, services inservices/, tools intools/
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 · 28 lines · 316 tokens per session scan A c61154dcdbfe
vidcap-mcp-server AGENTS.md is an instructions file published in the GitHub repository mrgoonie/vidcap-mcp-server (9 stars, last pushed 3mo ago), licensed MIT. It adds 316 tokens to every session, about $0.0016 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).