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/meltforce/freereps/verifynpx skills add meltforce/FreeReps --skill verifygit clone --depth 1 https://github.com/meltforce/FreeRepsWhat 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.00097 | $0.01036 |
| Opus 5 | $0.00048 | $0.00518 |
| Sonnet 5 | $0.00019 | $0.00207 |
| Haiku 4.5 | $0.00010 | $0.00104 |
Grade A, and why
verify scanned grade A with 1 finding 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sS "$F/actions/runs?limit=5" # -> run id, newest first How it starts
The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify
Run from the repo root. The order below is cheapest-first: a failure in step 1 makes the rest irrelevant.
1. Go
mkdir -p server/web/dist && touch server/web/dist/.gitkeep # only if dist is absent
cd server && go build ./... && go vet ./... && go test ./...
The stub matters: server/web.go embeds web/dist via go:embed, and without
the directory the build fails with an embed error that names the directive
rather than the missing directory.
go test ./... skips the integration tests. Those need a running TimescaleDB and
run with go test -tags integration ./... — run them when the change touches
server/internal/storage/ or a migration, because the unit tests do not execute
a single SQL statement against a real server.
2. golangci-lint
cd server && golangci-lint run ./...
CI pins v2.10.1 (.forgejo/workflows/ci.yml). A local version that differs can
pass where CI fails; on a disagreement, the pinned version decides.
3. Frontend
cd server/web && npm ci && npx tsc --noEmit && npm run build
npm run build runs tsc -b itself, so the separate tsc --noEmit is only
worth running on its own when you want the type errors without waiting for Vite.
4. Documents
tools/check-docs.sh --all
Checks the movement rule and status tokens in ROADMAP.md, ISO dates in the
tracked documents, and sweeps the repo for German text. It detects; it does not
prevent. On a German hit that is a verbatim quote of upstream output, add that
specific line to tools/check-docs.allow with a reason — do not weaken the
pattern in the script.
What CI repeats, and what it does not
.forgejo/workflows/ci.yml runs steps 1 through 4 on every push and PR against
main. It does not run the integration tests, and it does not build the iOS
app — that happens on GitHub via the mirror, in .github/workflows/ios.yml.
A green CI run on main continues into build and deploy to freereps-lxc. A
failure after the build stage means :edge may be in a broken state; the ntfy
alert in notify-deploy-failure carries the run URL.
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.
- 2d ago First seen · 96 lines · 97 tokens per session scan A c9f0dc5999c4
verify is a skill published in the GitHub repository meltforce/FreeReps (16 stars, last pushed 22d ago), licensed MIT. It adds 97 tokens to every session and 1,036 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
garmin-connect
Garmin Connect CLI for activities, health, body composition, workouts, devices, gear, goals, and more.
icuvisor-training
Use when answering endurance training questions with icuvisor MCP tools and intervals.icu data. Keeps answers grounded in tool results, handles athlete-local dates, stale data, subjective scales, safe writes, and workout/calendar workflows.
garmin-trainer
Adaptive 12-week training plan generator using Garmin Connect data. Creates structured workouts and schedules them on your Garmin calendar. Use this skill whenever the user asks about training plans, workout scheduling, race preparation, building fitness for upcoming events, or wants to generate/update their training…
Longevity Protocol
Assembles an evidence-tiered weekly longevity routine across the four pillars with the strongest healthspan data - sleep, zone 2 aerobic work, strength training, and dietary pattern - plus stress and connection, delivered as a filled weekly template with honest evidence labels. Use when someone asks "build me a…
Injury Prehab
Designs targeted prehab routines - sets, reps, and weekly placement - that build resilience at the four most common failure zones: shoulders, knees, lower back, and hips, matched to the user's training program. Use when someone says "my shoulders feel beat up from bench", "how do I bulletproof my knees for running"…
Mobility Routine
Builds a 10-15 minute daily floor-based mobility routine for desk workers, targeting the four zones sitting predictably stiffens - hips, thoracic spine, shoulders/neck, and ankles - with exact holds, reps, and a sequenced routine card. Use when someone says "I'm stiff from sitting all day", "my hips are tight", "fix…