hevy-mcp: Instructions file for Codex

AGENTS.md

hevy-mcp AGENTS.md is an instructions file for Codex, OpenCode from Alexisb1988/hevy-mcp. It costs 3,948 tokens per session, scanned A, a copy of hevy-mcp copilot-instructions.md, MIT.

Repository instructions for hevy-mcp, an MCP server that lets AI agents work with the Hevy fitness-tracking app. They describe the project's code structure, checks, and development rules.

In plain words
What is it for?
Use them when changing Hevy workout, routine, exercise-template, or folder features, or when building and committing changes in the repository.
Why use it?
They give coding agents project-specific guidance so they know which files to change, which files are generated, and which tests to run after sensitive updates.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions Claude Code.

This is Alexisb1988/hevy-mcp's own configuration. It tells Codex and OpenCode how to work on hevy-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything hevy-mcp configures →

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is import type { InferToolParams } from "../utils/tool-helpers.js";.

Reuse

Borrowing it

Nothing to install: this file belongs to Alexisb1988/hevy-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.

Copy the file
curl -O https://raw.githubusercontent.com/Alexisb1988/hevy-mcp/agent/promote-cloudflare-hosted-endpoint/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/Alexisb1988/hevy-mcp

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for hevy-mcp AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/alexisb1988/hevy-mcp/agents-md/github.svg)](https://agentmods.dev/instructions/alexisb1988/hevy-mcp/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/alexisb1988/hevy-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/alexisb1988/hevy-mcp/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for hevy-mcp AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/alexisb1988/hevy-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/alexisb1988/hevy-mcp/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 3,948 This file is loaded in full into every session.
When invoked 3,948 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 94% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.03948 $0.03948
Opus 5 $0.01974 $0.01974
Sonnet 5 $0.00790 $0.00790
Haiku 4.5 $0.00395 $0.00395

Measured 8d ago against content hash 989377d9c6b2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

hevy-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 8d 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.

Origin

This is a copy

94% identical to hevy-mcp copilot-instructions.md — 81 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

AGENTS.md · 415 lines

How it starts

The opening of the file, as written. The whole thing — 415 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Agent Instructions for hevy-mcp

ALWAYS follow these instructions first and only fallback to search or additional context if the information here is incomplete or found to be in error.

Project Overview

  • hevy-mcp is a Model Context Protocol (MCP) server for the Hevy Fitness API, enabling AI agents to manage workouts, routines, exercise templates, and folders via the Hevy API.
  • The codebase is TypeScript (Node.js v24+), with a clear separation between tool implementations (src/tools/), generated API clients (src/generated/), and utility logic (src/utils/).
  • API client code is generated from the OpenAPI spec using Kubb. Do not manually edit generated files.
  • Type Safety: The project uses Zod schema inference for type-safe tool parameters, eliminating manual type assertions and ensuring compile-time type safety.
  • MCP SDK internals sensitivity: src/utils/stdio-observability.ts depends on MCP SDK stdio internals (private fields such as _ondata/_readBuffer) for raw chunk instrumentation. Re-run the stdio observability test suite after any @modelcontextprotocol/sdk upgrade.

Git & Workflow Standards

  • Conventional Commits: AI agents (such as Claude Code, Antigravity, etc.) and developers must always use the conventional commit format (e.g., feat:, fix:, refactor:, build:, ci:, chore:, docs:, style:, test:) for all commits they generate or suggest.
  • No Direct Pushes to main (CRITICAL): Pushing directly to the main branch is strictly prohibited and blocked by branch protection. All development must be done on feature branches (e.g., feat/some-feature or fix/some-bug) and submitted via a Pull Request.
  • Changesets (CRITICAL): The project uses Changesets for versioning and releases.
    • RELEASE CADENCE: Merge the automated changeset-release/main ("Version Packages") Pull Request on a regular cadence (weekly is the default), not via ad-hoc frequent merges.
    • URGENT EXCEPTION: Security fixes and high-impact user-facing bug fixes may be released immediately outside the routine cadence.
    • WHEN TO USE: Every single PR/change that modifies source code or package dependencies MUST include a changeset file.
    • HOW TO CREATE BUMP CHANGESETS: Use npx changeset with patch/minor/major only for user-facing, runtime-visible changes.
    • NO-OP / NO-RELEASE CHANGES: For docs, CI config, internal tests, refactoring, and other internal-only changes, you MUST run npx changeset --empty.
    • CI ENFORCEMENT: Pull Requests are guarded by a CI check that runs npm run check:changeset (which runs npx changeset status --since=origin/<base_branch>). CI will fail if no changeset file is staged/committed.
    • VALIDATION: You can validate your changeset status locally by running npm run check:changeset. Make sure the changeset file is staged/committed.

Read the full file on GitHub · 415 lines

Changes

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.

  1. 8d ago First seen · 415 lines · 3,948 tokens per session scan A 989377d9c6b2

Subscribe to this mod's changes

hevy-mcp AGENTS.md is an instructions file published in the GitHub repository Alexisb1988/hevy-mcp (0 stars, last pushed yesterday), licensed MIT. It adds 3,948 tokens to every session, about $0.0197 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to hevy-mcp copilot-instructions.md, differing in 81 lines, and is treated as a copy.

Related

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.

vercel/next.js · 7,296 tokens

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.

openai/codex · 5,153 tokens

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).

microsoft/vscode · 6,785 tokens

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).

microsoft/vscode · 5,001 tokens

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.

langchain-ai/langchain · 4,469 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 3,737 tokens