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/check-technologies/mcp-server-check/agents-mdgit clone --depth 1 https://github.com/check-technologies/mcp-server-checkWrote 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/check-technologies/mcp-server-check/agents-md)<a href="https://agentmods.dev/instructions/check-technologies/mcp-server-check/agents-md"><img src="https://agentmods.dev/badge/instructions/check-technologies/mcp-server-check/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 | $0.00693 | $0.00693 |
| Opus 5 | $0.00347 | $0.00347 |
| Sonnet 5 | $0.00139 | $0.00139 |
| Haiku 4.5 | $0.00069 | $0.00069 |
Grade A, and why
mcp-server-check 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 3d 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 — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Cursor Cloud specific instructions
This repo is mcp-server-check: a Python (>=3.10) package providing both an MCP server
(mcp-server-check) and a CLI (check) for the Check Payroll API. It is managed with
uv; dependencies are locked in uv.lock. There is no
database, frontend, or other service — the only "backend" it talks to is the remote Check API
(https://sandbox.checkhq.com by default).
The update script runs uv sync --frozen, so dependencies and the .venv are already in place
when a session starts. Run all commands through uv run (they execute inside .venv).
Lint / test / build (see .github/workflows/ci.yml)
- Lint:
uv run ruff check src/ tests/anduv run ruff format --check src/ tests/ - Tests:
uv run pytest tests/— 465 tests. Tests need no API key or network; HTTP is mocked withrespx. - Optional git hooks mirroring CI lint:
uv run pre-commit install(config in.pre-commit-config.yaml).
Running the services
- MCP server:
uv run mcp-server-check. RequiresCHECK_API_KEY(exits with an error otherwise). Defaults to stdio transport and "dynamic" tool mode (exposes 3 meta-tools:search_tools,list_toolsets,run_tool). Env knobs:CHECK_TOOL_MODE=all(legacy all-tools),CHECK_TRANSPORT,CHECK_ENV/CHECK_API_BASE_URL,CHECK_READ_ONLY,CHECK_TOOLSETS,CHECK_TOOLS,CHECK_EXCLUDE_TOOLS. - CLI:
uv run check ...(seeCLI.md).check --help,check --version, andcheck init <target>work without a key; any command that hits the API needsCHECK_API_KEY(passed via--api-keyor env). Defaults to the sandbox environment.
Non-obvious notes
- Tests and
--help/initwork offline; live API calls (and starting the MCP server) require a validCHECK_API_KEYsecret. - Prefer a sandbox key for testing. Sandbox (
https://sandbox.checkhq.com) is the default environment for both the CLI and MCP server, supports thesimulate-*endpoints, and write operations there move no real money. A production key (--env production/https://api.checkhq.com) touches real payroll data — only use it for read-only checks. - To exercise tool round-trips without any key, mock the HTTP layer with
respx(as the tests do) and drive the in-memory server viafastmcp'sClient(mcp). uv.lockresolvesfastmcpto a 3.x release even thoughpyproject.tomlonly pins>=2.0.0; useuv sync --frozento stay consistent with CI.
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.
- 3d ago First seen · 41 lines · 693 tokens per session scan A f7714254eb04
mcp-server-check AGENTS.md is an instructions file published in the GitHub repository check-technologies/mcp-server-check (18 stars, last pushed 5d ago), licensed MIT. It adds 693 tokens to every session, about $0.0035 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
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.