Borrowing it
Nothing to install: this file belongs to chrischall/tempo-api-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/tempo-api-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/chrischall/tempo-api-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/tempo-api-mcp/claude-md)<a href="https://agentmods.dev/instructions/chrischall/tempo-api-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/chrischall/tempo-api-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.02660 | $0.02660 |
| Opus 5 | $0.01330 | $0.01330 |
| Sonnet 5 | $0.00532 | $0.00532 |
| Haiku 4.5 | $0.00266 | $0.00266 |
Grade A, and why
tempo-api-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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
tempo-api-mcp
MCP server exposing the Tempo REST API (v4) to Claude via stdio transport. Forty-odd tools for worklogs, plans, teams, accounts, projects, timesheet approvals, periods, schedules, and Tempo configuration.
Commands
npm run build # tsc + esbuild bundle → dist/index.js + dist/bundle.js
npm test # tsc typecheck + vitest run
npm run test:watch # vitest watch
npm run test:coverage # tsc typecheck + v8 coverage (text + html)
Run locally (requires built dist):
TEMPO_API_TOKEN=xxx npm run dev # node dist/index.js
Tool naming
All tools are prefixed tempo_ (e.g. tempo_get_worklogs, tempo_create_worklog, tempo_get_timesheet_approval_status).
Architecture
src/
index.ts # entry — `runMcp({ name, version, deps: client, tools: [...] })` from @chrischall/mcp-utils
client.ts # TempoClient — thin wrapper over `createApiClient` (mcp-utils); Bearer auth, retry, timeout
tools/
worklogs.ts # worklogs CRUD + search + by-user/project/issue/team/account
plans.ts # plans CRUD (resource allocations)
teams.ts # teams CRUD + team-memberships list/search
accounts.ts # accounts CRUD + search + categories
projects.ts # projects, timesheet approvals (read + submit/approve/reject/reopen/recall), logs, periods, user-schedule, global config, work attributes, roles
Each tool file exports register(server: McpServer, client: TempoClient) and calls server.registerTool(name, def, handler) for each tool. To add a new domain, create src/tools/<name>.ts with a register export and add it to the tools array in src/index.ts.
Most plumbing lives in @chrischall/mcp-utils, not this repo: runMcp (boots the high-level McpServer + stdio transport, prints the AI-maintained banner to stderr), createApiClient/fetchJson (Bearer auth, retry, timeout, auth/rate-limit error mapping), loadDotenvSafely, readEnvVar (placeholder-defended env parsing), buildOptionalBody (body builders), and textResult/rawTextResult (tool output). TempoClient (client.ts) just configures createApiClient for Tempo; the tool modules still receive the SDK's high-level McpServer.
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 · 127 lines · 2,660 tokens per session scan A 83549b3627d3
tempo-api-mcp CLAUDE.md is an instructions file published in the GitHub repository chrischall/tempo-api-mcp (0 stars, last pushed yesterday), licensed MIT. It adds 2,660 tokens to every session, about $0.0133 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
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).
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).
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.