Borrowing it
Nothing to install: this file belongs to snoozelieb/coach-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/snoozelieb/coach-mcp/main/.claude/skills/acwr-recompute/SKILL.mdgit clone --depth 1 https://github.com/snoozelieb/coach-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/snoozelieb/coach-mcp/acwr-recompute)<a href="https://agentmods.dev/skills/snoozelieb/coach-mcp/acwr-recompute"><img src="https://agentmods.dev/badge/skills/snoozelieb/coach-mcp/acwr-recompute/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/snoozelieb/coach-mcp/acwr-recompute"><img src="https://agentmods.dev/badge/skills/snoozelieb/coach-mcp/acwr-recompute.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.00069 | $0.00562 |
| Opus 5 | $0.00034 | $0.00281 |
| Sonnet 5 | $0.00014 | $0.00112 |
| Haiku 4.5 | $0.00007 | $0.00056 |
Grade A, and why
acwr-recompute 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 10d 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.
What it actually says
Recomputing stored ACWR history (supervised)
scripts/recompute_acwr_history.py rewrites the acwr field of every snapshot
entry in fitness_history.json — the total block AND every per-sport block —
from raw daily_loads using the rolling 7d:28d model imported from
coach.fitness (never a reimplementation). ctl/atl/tsb are left
untouched: their EWMA scale is self-consistent and targets are tuned against it.
This is a supervised migration, not maintenance. It was built for the
2026-06-10 ACWR cutover; reach for it again only if the primary model changes
or historical daily_loads were backfilled/repaired.
Procedure — in this order
-
Timestamped backup first (execution rule for ANY migrating change to live coaching data — it is gitignored and irreplaceable):
cp -r data "data-backups/backup-$(date +%Y%m%d-%H%M)" -
Dry-run and actually read it (default mode; writes nothing):
python scripts/recompute_acwr_history.py --checkReview the printed change list WITH the user — zone flips (
optimal↔elevated, the "sweet spot" boundary, as labeled byclassify_acwr_zone) are the changes that alter coaching behavior. Get explicit approval before applying. -
Apply:
python scripts/recompute_acwr_history.py --apply--applytakes a one-timefitness_history.json.pre-acwr-cutover.bakbeside the file (never overwritten — storage backup convention) and writes atomically/locked viacoach.storage. -
Verify: re-run
--check(should report no changes), thenpython -m pytest -q, then have the running MCP server reconnected so the snapshot serves recomputed values.
--data-dir path/to/data targets a non-default data directory (e.g. a restored
backup for a rehearsal run — rehearse there when the change list is large).
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.
- 10d ago First seen · 54 lines · 69 tokens per session scan A 6d1d8ba446d3
acwr-recompute is a skill published in the GitHub repository snoozelieb/coach-mcp (2 stars, last pushed 14d ago), licensed MIT. It adds 69 tokens to every session and 562 once invoked, about $0.0003 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.
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…