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/blencorp/capture-mcp-server/claude-mdgit clone --depth 1 https://github.com/blencorp/capture-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/blencorp/capture-mcp-server/claude-md)<a href="https://agentmods.dev/instructions/blencorp/capture-mcp-server/claude-md"><img src="https://agentmods.dev/badge/instructions/blencorp/capture-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.1 | $0.01563 | $0.01563 |
| Opus 5 | $0.00781 | $0.00781 |
| Sonnet 5 | $0.00313 | $0.00313 |
| Haiku 4.5 | $0.00156 | $0.00156 |
Grade A, and why
capture-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 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Development Commands
Building and Running
npm run build- Compiles TypeScript to dist/ directorynpm start- Runs the compiled server (requires build first)npm run dev- Development mode with ts-node (auto-reload with nodemon)
Project Configuration
- Uses ES modules (
"type": "module"in package.json) - TypeScript compilation target: ES2020
- Output directory:
dist/ - Source directory:
src/
Architecture Overview
This is a Model Context Protocol (MCP) server that captures federal procurement and spending data through 34 specialized tools. The architecture follows a modular tool-based design:
Core Components
Server (src/server.ts)
- MCP server using
@modelcontextprotocol/sdk - Uses stdio transport for Claude Desktop integration
- Handles tool registration and execution through centralized registry
Tool Architecture (src/tools/)
- Modular tool system with six categories:
reference-tools.ts- 1 static FPDS reference tool (lookup_reference_code; no key, no network)sam-tools.ts- 4 SAM.gov API tools (entities, opportunities, details, exclusions)usaspending-tools.ts- 6 USASpending.gov API tools (awards, spending, budgets, recipient search,get_award_detailverification,aggregate_contractsgrouping)tango-tools.ts- 12 Tango API tools (contracts, grants, vendor profiles, opportunities, spending summaries, GAO protests + detail, IDVs + child/task-order drill-down, vehicle catalog, OTAs, entity time-series metrics). Set-aside filtering is exact on FPDS codes; cursor pagination via the TangonextURL.highergov-tools.ts- 9 HigherGov tools (forecast/opportunity/contract/people search, saved-search listing, opportunity documents, single-record lookups). Responses are normalized to lowercase agency/vehicle/set-aside slugs viautils/highergov-slugs.ts.get_*tools cache for 15 min in an in-process LRU.join-tools.ts- 2 cross-API tools (entity+awards, opportunity+context)
- Response conventions (see
utils/envelope.tsand docs/fix-plan.md): every list tool echoesfilters.upstreamvsfilters.client_side, nulls untrustworthy totals (total_upstream_unfiltered/total_upstream_unverified+ warnings), labelscount_unitanddate_field, and returns onenext_cursorshape.tools/index.tsrejects unknown/mistyped parameters with a structured bad_request.utils/fpds-codes.tsis the FPDS code table;docs/upstream-api-notes.mdrecords which upstream params are verified to bind (runnpm run capture-fixtureswith live keys to re-probe). - Each tool module exports
getTools()andcallTool()methods - Central registry in
tools/index.tsmanages all tool registration
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 · 131 lines · 1,563 tokens per session scan A d4840fb09797
capture-mcp-server CLAUDE.md is an instructions file published in the GitHub repository blencorp/capture-mcp-server (34 stars, last pushed 9d ago), licensed MIT. It adds 1,563 tokens to every session, about $0.0078 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
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).