What is NYC-Opendata-Capital-Projects-MCP AGENTS.md?

Repository instructions for an MCP server that serves New York City capital-project data from four public datasets through a local DuckDB database. DuckDB is a database designed to query files and analytical data locally.

They help developers understand the data model, run tests, update the live database, and keep feature documentation current.

They give coding agents the project rules, domain definitions, testing commands, and data-keying assumptions needed to change the server safely.

How WillHsiaoNYC/NYC-Opendata-Capital-Projects-MCP configures Codex an

Reuse

Borrowing it

Nothing to install: this file belongs to WillHsiaoNYC/NYC-Opendata-Capital-Projects-MCP. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/WillHsiaoNYC/NYC-Opendata-Capital-Projects-MCP/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/WillHsiaoNYC/NYC-Opendata-Capital-Projects-MCP

Made for: Codex, OpenCode.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/willhsiaonyc/nyc-opendata-capital-projects-mcp/agents-md/github.svg)](https://agentmods.dev/instructions/willhsiaonyc/nyc-opendata-capital-projects-mcp/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/willhsiaonyc/nyc-opendata-capital-projects-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/willhsiaonyc/nyc-opendata-capital-projects-mcp/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/willhsiaonyc/nyc-opendata-capital-projects-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/willhsiaonyc/nyc-opendata-capital-projects-mcp/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 1,430 This file is loaded in full into every session.

When invoked 1,430 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.01430	$0.01430
Opus 5.5	$0.00572	$0.00572
Sonnet 5.5	$0.00286	$0.00286
Haiku 4.5	$0.00143	$0.00143

Measured 2mo ago against content hash 5d7cd2228b17, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

NYC-Opendata-Capital-Projects-MCP 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 2mo 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.

AGENTS.md · 99 lines

How it starts

The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.

OD-CPD MCP — project guide for Codex

NYC Capital Projects data (4 Socrata datasets) served over a local DuckDB as an MCP server.

Read this first

docs/FEATURES.md is the canonical inventory of the MCP's tools and the domain rules it encodes — PID↔FMS many-to-many, the sponsor-driven category taxonomy, signed-value reporting, reporting cadence, the (managing_agency, fms_id) budget grain, etc. Read it before answering data questions or changing behavior.
Keep docs/FEATURES.md current. Whenever the MCP gains a tool, a built-in domain rule, or a taxonomy/behavior change, update the relevant section and bump its "Last updated" date — ideally in the same PR.
Every aggregation in materialize.py encodes a keying assumption — which entity (budget line, PID, pair, snapshot) each published column attaches to. Verify the keying before changing it.

Running & testing

Tests: uv run pytest (fallback: PYTHONPATH=src python -m pytest).
The MCP server is stdio, launched by the client as uv run --directory <repo> od-cpd-server with PYTHONPATH=<repo>/src. Bare uv run od-cpd-server can fail with ModuleNotFoundError when the editable .pth is missing or hidden (e.g. under iCloud), so always set PYTHONPATH=src.
Code changes do not reach the running server until it is reconnected — it's a stdio subprocess. Reconnect via /mcp (or restart the client) to load new code.

Updating the live database

od-cpd init / od-cpd update re-download all four datasets from Socrata (full ingest).
To apply YAML / materialize.py changes without re-downloading, re-materialize the existing raw tables via the atomic-swap pattern: copy var/cpd.duckdb → a shadow file, open it read-write, run materialize.materialize_all(con), then ingest.atomic_swap(shadow, db). Never open the live DB read-write directly while the MCP may touch it — the shadow + atomic swap keeps the running server safe.

Architecture orientation

Read the full file on GitHub · 99 lines

Changes

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.

2mo ago First seen · 99 lines · 1,430 tokens per session scan A 5d7cd2228b17

Subscribe to this mod's changes

NYC-Opendata-Capital-Projects-MCP AGENTS.md is an instructions file published in the GitHub repository WillHsiaoNYC/NYC-Opendata-Capital-Projects-MCP (1 stars, last pushed 29d ago), licensed MIT. It adds 1,430 tokens to every session, about $0.0057 per session on Opus 5.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-09-07.

Databases

NYC-Opendata-Capital-Projects-MCP AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
NYC-Opendata-Capital-Projects-MCP AGENTS.mdWillHsiaoNYC/NYC-Opendata-Capital-Projects-MCP	Instructions file	1	29d ago	MIT	A	1,430	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	9,719	GitHub Copilot
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	5,516	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	today	MIT	A	4,680	Codex, OpenCode
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	3,093	GitHub Copilot
vscode model-prompts.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	2,022	GitHub Copilot

NYC-Opendata-Capital-Projects-MCP: Instructions file for Codex