log

A workout-logging command that turns a natural-language training description into entries in Gymtracker, a workout-tracking service.

In plain words
What is it for?
Creating or reusing today’s workout, adding exercises and sets, including optional effort details, completing the session, and summarizing it.
Why use it?
It removes the need to enter each exercise, set, repetition, and weight manually, while asking when required numbers are missing.

Command

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.

agentmods
npx agentmods add commands/benzalglez/gymtracker-plugin/log
Clone the repo
git clone --depth 1 https://github.com/benzalglez/gymtracker-plugin
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 227 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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 $0.00011 $0.00227
Opus 5 $0.00005 $0.00113
Sonnet 5 $0.00002 $0.00045
Haiku 4.5 $0.00001 $0.00023

Measured yesterday against content hash eb9c21e9d83a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

log 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/commands/log.md · 15 lines

What it actually says

The user wants to log a training session in Gymtracker. Their description: $ARGUMENTS

Do this:

  1. Call gym_whoami to confirm the connection works.
  2. If no session exists for today, call gym_create_session with plannedFor set to today's ISO date (and a title if the user named the workout). Otherwise reuse today's session from gym_list_sessions.
  3. For each exercise mentioned, call gym_add_session_exercise (set nameSnapshot and an incrementing position; look up a catalogItemId with gym_search_catalog when possible).
  4. For each set, call gym_add_set with reps and weightKg (plus rpe/rir if given).
  5. When the user says they're done, call gym_complete_session.
  6. Summarize what was logged. Never invent numbers — ask if a value is missing.
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. yesterday First seen · 15 lines · 11 tokens per session scan A eb9c21e9d83a

Subscribe to this mod's changes

log is a command published in the GitHub repository benzalglez/gymtracker-plugin (0 stars, last pushed 2mo ago), licensed MIT. It adds 11 tokens to every session and 227 once invoked, about $0.0001 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-31.