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/rwestergren/hevy-mcp/claude-mdgit clone --depth 1 https://github.com/rwestergren/hevy-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/rwestergren/hevy-mcp/claude-md)<a href="https://agentmods.dev/instructions/rwestergren/hevy-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/rwestergren/hevy-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 | $0.00947 | $0.00947 |
| Opus 5 | $0.00474 | $0.00474 |
| Sonnet 5 | $0.00189 | $0.00189 |
| Haiku 4.5 | $0.00095 | $0.00095 |
Grade A, and why
hevy-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 4d 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project Overview
This is a Model Context Protocol (MCP) server for the Hevy fitness tracking API. It provides tools for AI assistants to interact with workouts, routines, exercise templates, folders, and webhook subscriptions through the Hevy API.
Key Commands
Development
npm run dev- Start development server with hot reloadingnpm run build- Build the project for productionnpm start- Run the built project
Code Quality
npm run check- Run oxlint linter and oxfmt formatter (auto-fixes issues)npm run check:types- TypeScript type checking without emitting filesnpm test- Runs Vitest against all*.test.tsfiles (includingtests/integration/**). Integration tests will fail by design withoutHEVY_API_KEY. See the "Testing" section inREADME.mdfor CI requirements and secret configuration.
API Client Generation
npm run export-specs- Export OpenAPI specificationnpm run build:client- Generate API client using Kubb from OpenAPI spec
Testing Variants
npx vitest run --exclude tests/integration/**- Unit tests onlynpx vitest run tests/integration- Integration tests only (requires HEVY_API_KEY)npx vitest run --coverage- Tests with coverage report
Architecture
Core Structure
- Entry Point:
src/index.ts- MCP server setup and tool registration - Tools:
src/tools/- MCP tool implementations organized by domain:workouts.ts- Workout CRUD operationsroutines.ts- Routine managementtemplates.ts- Exercise template accessfolders.ts- Routine folder organizationwebhooks.ts- Webhook subscription management
- Utils:
src/utils/- Shared utilities for HTTP client, formatting, and error handling - Generated Code:
src/generated/- Auto-generated API client from OpenAPI spec
Client Architecture
The project uses a generated API client via Kubb that creates:
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.
- 4d ago First seen · 109 lines · 947 tokens per session scan A 2d310bd08d93
hevy-mcp CLAUDE.md is an instructions file published in the GitHub repository rwestergren/hevy-mcp (0 stars, last pushed 4mo ago), licensed MIT. It adds 947 tokens to every session, about $0.0047 per session on Opus 5. A static security scan graded it A with 0 findings. It comes from a forked repository.
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).
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.
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).