Borrowing it
Nothing to install: this file belongs to chrischall/ioffice-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/chrischall/ioffice-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/chrischall/ioffice-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/chrischall/ioffice-mcp/claude-md)<a href="https://agentmods.dev/instructions/chrischall/ioffice-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/chrischall/ioffice-mcp/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.02145 | $0.02145 |
| Opus 5 | $0.01073 | $0.01073 |
| Sonnet 5 | $0.00429 | $0.00429 |
| Haiku 4.5 | $0.00215 | $0.00215 |
Grade A, and why
ioffice-mcp 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 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ioffice-mcp
MCP server exposing iOffice workspace/facility management APIs to Claude. Uses stdio transport.
Commands
npm run build # tsc + esbuild bundle → dist/index.js + dist/bundle.js
npm test # Run tests (vitest)
npm run test:watch # Watch mode
npm run test:coverage # Coverage report (100% thresholds enforced)
npm run dev # node --env-file=.env dist/index.js (requires built dist)
Run locally (requires built dist):
IOFFICE_HOST=tenant.ioffice.com IOFFICE_TOKEN=xxx node dist/index.js
Tool naming
All tools are prefixed io_ (e.g. io_list_buildings, io_create_reservation, io_checkin_visitor).
Architecture
src/
index.ts # MCP server entry — runMcp() from @chrischall/mcp-utils, registers all tool modules, stdio transport
client.ts # IOfficeClient (thin wrapper over createApiClient from @chrischall/mcp-utils) + re-exported buildQueryString/buildOptionalBody + local optionalBody helper
tools/
buildings.ts # io_{list,get,create,update,delete}_building
floors.ts # io_{list,get,create,update,delete}_floor
spaces.ts # io_{list,get,create,update,delete}_space
users.ts # io_{list,get,create,update,delete}_user
reservations.ts # io_{list,get,create,update,delete,checkin,checkout}_reservation
visitors.ts # io_{list,get,create,update,checkin,checkout}_visitor
maintenance.ts # io_{list,get,create,update,accept,start,complete,archive}_maintenance_request
mail.ts # io_{list,get,create,deliver,return}_mail
moves.ts # io_{list,get,create,update,approve,cancel}_move
Each tool module exports a register<Domain>Tools(server, client) function that calls server.registerTool(...) with a zod input schema and a handler. index.ts constructs one IOfficeClient and hands it to runMcp({ deps: client, tools: [...] }), which passes it to every register call. Add new domains by mirroring this pattern (and add them to the tools array in index.ts).
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 · 136 lines · 2,145 tokens per session scan A 6c72a923edf4
ioffice-mcp CLAUDE.md is an instructions file published in the GitHub repository chrischall/ioffice-mcp (1 stars, last pushed 2d ago), licensed MIT. It adds 2,145 tokens to every session, about $0.0107 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
vibe-coding-prompt-template backend.instructions.md
Instructions for KhazP/vibe-coding-prompt-template: Read AGENTS.md, agentdocs/techstack.md, and agentdocs/codepatterns.md.
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.