Borrowing it
Nothing to install: this file belongs to ikeike443/hevy-fitness-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/ikeike443/hevy-fitness-mcp/main/.claude/skills/hevy-routine-builder/SKILL.mdgit clone --depth 1 https://github.com/ikeike443/hevy-fitness-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/ikeike443/hevy-fitness-mcp/hevy-routine-builder)<a href="https://agentmods.dev/skills/ikeike443/hevy-fitness-mcp/hevy-routine-builder"><img src="https://agentmods.dev/badge/skills/ikeike443/hevy-fitness-mcp/hevy-routine-builder/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.
<a href="https://agentmods.dev/skills/ikeike443/hevy-fitness-mcp/hevy-routine-builder"><img src="https://agentmods.dev/badge/skills/ikeike443/hevy-fitness-mcp/hevy-routine-builder.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.01875 |
| Opus 5 | $0.00000 | $0.00937 |
| Sonnet 5 | $0.00000 | $0.00375 |
| Haiku 4.5 | $0.00000 | $0.00187 |
Grade A, and why
hevy-routine-builder 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 11d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hevy Routine Builder
A standard workflow and rule set for creating/updating Hevy routines (workout plan templates) through this server's MCP tools.
Overview
- Check the user's actual training history (
list_workouts/get_workout_detail, orget_exercise_historyfor one exercise across all past workouts) to learn real working weights for the relevant exercises. - Pick exercises, and resolve each one's
exerciseTemplateIdviasearch_exercise_templates— never guess an ID. If the search returns multiple plausible candidates, ask the user which one they mean. - Decide weight, reps, and rest time per the rules below.
- Before writing anything, show the full plan as a table and get explicit confirmation from the user.
- Confirm the destination folder (see "Folder handling" below).
- Only after both are confirmed, call
create_routine(new) orupdate_routine(overwrite) withconfirm: true.
Do not skip steps 4–5 and set confirm: true regardless. This tool's confirm flag exists specifically so a call with confirm: false/omitted never touches Hevy — it returns the exact payload that would be sent instead, as a dryRun: true preview. Use that dry-run response as what you show the user in step 4, then re-call with confirm: true only after they say yes. This is a real write to the user's live Hevy account with no way to undo it automatically (see "Known limitations" below).
Choosing weights (priority order)
Always prefer the user's real logged history over a computed estimate.
- Prefer the user's own past logs for the same exercise. Call
get_exercise_history(orget_workout_detailon a relevant recent workout) and use a recent working weight/rep/RPE combination close to what you're proposing. - If there's no history for that exact exercise, infer from a closely related exercise/movement pattern (e.g. no data for a chest-supported row variant → use their regular incline dumbbell row numbers as a starting point).
- If there's no history for anything closely related, reason from a combination of nearby-muscle-group exercises the user has logged and general population norms for an intermediate lifter — and say so explicitly.
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.
- 11d ago First seen · 87 lines · 0 tokens per session scan A fb658764e2ac
hevy-routine-builder is a skill published in the GitHub repository ikeike443/hevy-fitness-mcp (0 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,875 tokens. 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…