A Gymtracker connection and coaching helper for an AI coding assistant. It uses your Gymtracker URL and API token to access your training data; delete actions are off unless enabled.

Reading and updating Gymtracker data, and getting help with training decisions or plans.

It keeps workout data and coaching available in the same assistant you use for other tasks, so you do not have to switch tools or enter it manually.

gym — Plugin by benzalglez

Install

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.

Claude Code

/plugin marketplace add benzalglez/gymtracker-plugin

agentmods

npx agentmods add plugins/benzalglez/gymtracker-plugin/gym

Clone the repo

git clone --depth 1 https://github.com/benzalglez/gymtracker-plugin

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.

When invoked not measured Not applicable: nothing here is loaded into a session.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Security

Grade A, and why

gym 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 yesterday.

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.

plugins/gym/.claude-plugin/plugin.json · 31 lines

What it actually says

{
  "name": "gym",
  "description": "Gymtracker MCP server + coaching skill",
  "author": { "name": "Codin Team" },
  "homepage": "https://gitlab.com/codin-public/gymtracker-plugin",
  "repository": "https://gitlab.com/codin-public/gymtracker-plugin",
  "license": "MIT",
  "keywords": ["gym", "fitness", "mcp", "gymtracker"],
  "userConfig": {
    "GYMTRACKER_URL": {
      "type": "string",
      "title": "Gymtracker URL",
      "description": "Base URL of your Gymtracker Worker (e.g. https://gym.example.com)",
      "required": true
    },
    "GYMTRACKER_TOKEN": {
      "type": "string",
      "title": "Gymtracker API token",
      "description": "API token created from your Gymtracker /api/tokens page",
      "required": true,
      "sensitive": true
    },
    "GYMTRACKER_ALLOW_DELETE": {
      "type": "string",
      "title": "Allow delete tools",
      "description": "Set to 1 to also expose destructive delete tools (off by default)",
      "required": false
    }
  }
}

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.

yesterday First seen · 31 lines scan A 7443592fa02d

Subscribe to this mod's changes

gym is a plugin published in the GitHub repository benzalglez/gymtracker-plugin (0 stars, last pushed 2mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.

Backend and APIs

gym

Getting it into your agent

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other plugins, from other repositories

nextjs

nextjs

claude-plugins-official

knowledge-work-plugins

ecc

ecc