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 skills/chrisdoc/hevy-mcp/hevy-clinpx skills add chrisdoc/hevy-mcp --skill hevy-cligit clone --depth 1 https://github.com/chrisdoc/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/skills/chrisdoc/hevy-mcp/hevy-cli)<a href="https://agentmods.dev/skills/chrisdoc/hevy-mcp/hevy-cli"><img src="https://agentmods.dev/badge/skills/chrisdoc/hevy-mcp/hevy-cli.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.00038 | $0.01343 |
| Opus 5 | $0.00019 | $0.00672 |
| Sonnet 5 | $0.00008 | $0.00269 |
| Haiku 4.5 | $0.00004 | $0.00134 |
Grade A, and why
hevy-cli 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 5d 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hevy CLI
Use this skill to manage workouts in the Hevy app. The CLI supports reads, creates, and updates. Deletion is unsupported.
1. Install or run the published package
# One-off use; npm downloads the published package when needed.
npx @chrisdoc/hevy-cli --help
# Local project install.
npm i @chrisdoc/hevy-cli
npx hevy --help
# Persistent global install.
npm i -g @chrisdoc/hevy-cli
hevy --help
The package requires Node.js 24 or newer. Use npx --yes @chrisdoc/hevy-cli ... in non-interactive scripts. Installation is verified
when npx @chrisdoc/hevy-cli --version or hevy --version prints a version.
2. Configure the API key
The CLI reads credentials only from HEVY_API_KEY:
export HEVY_API_KEY='<your-hevy-api-key>'
Keep the key out of command arguments, JSON payloads, URLs, shell history,
screenshots, logs, and responses. --help and --version work without it.
3. Choose a route
Read routes:
userworkouts list,workouts get,workouts count,workouts eventsroutines list,routines getexercises search,exercises get,exercises historymeasurements list,measurements getsummary
Create/update routes:
workouts create,workouts update <workout-id>routines create,routines update <routine-id>exercises createfolders createmeasurements create <YYYY-MM-DD>,measurements update <YYYY-MM-DD>
The CLI exposes no delete, update-exercise-template, or update-folder routes. If a user requests deletion of any resource, explain that deletion is not supported by the CLI or the Hevy API integration. Suggest a supported alternative, such as archiving the resource in Hevy if available or replacing it.
Run route help whenever a flag or argument is uncertain:
npx @chrisdoc/hevy-cli <command> --help
Use the narrowest read route and date/page range that answers the question.
Use --json when output will be searched, filtered, or piped.
For exercise work, search first and use the exact returned template ID. Create a custom exercise only when the required movement is absent:
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.
- 5d ago First seen · 151 lines · 38 tokens per session scan A 5792ba956899
hevy-cli is a skill published in the GitHub repository chrisdoc/hevy-mcp (451 stars, last pushed today), licensed MIT. It adds 38 tokens to every session and 1,343 once invoked, about $0.0002 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 skills, from other repositories
verify
Run the checks that have to pass before a FreeReps commit lands — Go build, vet, tests and golangci-lint, the frontend type check and build, and the document contract check. Triggers — "verify", "prüf das durch", "vor dem commit", "läuft das durch", "check before committing", "run the checks", "does CI pass". Not for…
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
specflow-use
To connect Rosetta with Grid Dynamics SpecFlow MCP; only when SpecFlow is mentioned and the MCP is installed.
planning-and-task-breakdown
Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.
qa-knowledge
To run QA engineering — requirements/gap analysis, scenario & spec design, test implementation, failure triage — over the QA knowledge base.
ue-mcp-epic-routing
Use when deciding between ue-mcp's native category actions and Epic's wrapped ToolsetRegistry tools (the epic actions, incl. the Blueprint graph DSL) for a task in Unreal. Pulls in when authoring Blueprint graph bodies, or any time both a native action and an epic action could do the job and you need to pick.