Borrowing it
Nothing to install: this file belongs to fbdo/business-day-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.
curl -O https://raw.githubusercontent.com/fbdo/business-day-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/fbdo/business-day-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/fbdo/business-day-mcp/agents-md)<a href="https://agentmods.dev/instructions/fbdo/business-day-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/fbdo/business-day-mcp/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.02187 | $0.02187 |
| Opus 5 | $0.01094 | $0.01094 |
| Sonnet 5 | $0.00437 | $0.00437 |
| Haiku 4.5 | $0.00219 | $0.00219 |
Grade A, and why
business-day-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 7d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — business-day-mcp
A navigation map for AI coding assistants. For deeper reference, open the per-topic files under .agents/summary/ (start with .agents/summary/index.md).
Table of Contents
- What this repo is — one-paragraph scope
- Directory Map — where code lives
- Key Entry Points — start here when tracing behavior
- Subsystems — brief per-area summaries with file pointers
- Repo-Specific Patterns — things that deviate from Python defaults
- Config Files Worth Knowing — what each file controls
- Safety Invariants — do-not-break rules
- Custom Instructions — human-maintained operational notes
What this repo is
An MCP (Model Context Protocol) server that exposes 9 read-only tools for business-day and holiday arithmetic across 60+ countries. Single Python package, stdio transport via FastMCP, all country knowledge delegated to the holidays library.
Directory Map
business-day-mcp/
├── src/business_day_mcp/
│ ├── server.py # ★ all tool logic + helpers (single source of behavior)
│ ├── __init__.py # re-exports main, mcp, __version__
│ └── __main__.py # `python -m business_day_mcp` shim
├── tests/ # one file per concern — see Subsystems
├── .github/workflows/
│ ├── ci.yml # lint / typecheck / security / test matrix / build
│ └── publish.yml # tag-triggered PyPI publish via Trusted Publisher
├── .agents/summary/ # generated per-topic docs (see index.md)
├── pyproject.toml # deps + all tool config (ruff/mypy/pytest/bandit/coverage)
├── .pre-commit-config.yaml
├── .secrets.baseline # detect-secrets baseline
└── uv.lock # committed lockfile
Key Entry Points
| Question | Open |
|---|---|
| "How is the server started?" | src/business_day_mcp/server.py → main() (calls mcp.run(), stdio) |
| "What tools exist?" | server.py — search for mcp.tool( (9 registrations) |
| "What's the CLI command?" | pyproject.toml → [project.scripts] → business-day-mcp |
| "What's the response shape of tool X?" | .agents/summary/interfaces.md |
| "Why isn't there a cache?" | .agents/summary/architecture.md → Principle #10 |
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.
- 7d ago First seen · 128 lines · 2,187 tokens per session scan A b7270b98b9cc
business-day-mcp AGENTS.md is an instructions file published in the GitHub repository fbdo/business-day-mcp (0 stars, last pushed 4mo ago), licensed MIT. It adds 2,187 tokens to every session, about $0.0109 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
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).
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.
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.