A visual weekly running-plan card showing seven days of workouts, rest, distances, pacing, heart-rate zones, and each session's purpose. A periodized plan divides training into phases that change as a race approaches.

Use it to review or print this week's schedule after creating or adapting a plan, including easy runs, long runs, speed work, recovery, cross-training, and rest.

It turns a detailed training plan into a clear, print-ready view of the current week. It also keeps the week's sessions tied to an existing goal and plan.

pb-week — Skill for Claude Code by seungwee-choi

Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code

/plugin marketplace add seungwee-choi/oh-my-personal-best

Claude Code

/plugin install oh-my-personal-best

Made for: Claude Code.

Or install oh-my-personal-best, the plugin that ships this one along with the rest of its 11 skills, 11 commands, 8 agents.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/seungwee-choi/oh-my-personal-best/pb-week/github.svg)](https://agentmods.dev/skills/seungwee-choi/oh-my-personal-best/pb-week)

Your own site

<a href="https://agentmods.dev/skills/seungwee-choi/oh-my-personal-best/pb-week"><img src="https://agentmods.dev/badge/skills/seungwee-choi/oh-my-personal-best/pb-week/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/seungwee-choi/oh-my-personal-best/pb-week"><img src="https://agentmods.dev/badge/skills/seungwee-choi/oh-my-personal-best/pb-week.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 16 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 811 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00016	$0.00811
Opus 5	$0.00008	$0.00405
Sonnet 5	$0.00003	$0.00162
Haiku 4.5	$0.00002	$0.00081

Measured 12d ago against content hash f29b61fd364c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

pb-week 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 12d 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.

skills/pb-week/SKILL.md · 65 lines

How it starts

The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.

<Use_When>

The runner asks for "this week", "weekly plan", "training schedule", "주간 계획", "이번 주 훈련표", "week card"
After /pb-plan or weekly-adapt produces/updates the week </Use_When>

<Do_Not_Use_When>

No plan or goal exists yet → route to /pb-plan first (a week is derived from the periodized plan).
The runner wants only today's single session → use /pb-today (session-coach). </Do_Not_Use_When>

<Data_contract> The week is stored at $OMPB_HOME/plan-week.json as the PLAN_DATA object the template consumes:

{ "athlete": {"label","experience"}, "today": "YYYY-MM-DD",
  "goal": {"event","target_time","race_date","weeks_to_race"},
  "week": {"plan_week","total_weeks","phase","start_date","end_date","target_km","prev_week_km","ramp_pct","focus"},
  "days": [ {"dow","date","type","title","distance_km","pace","hr_zone","structure","purpose","done"} ...×7 ],
  "coach_notes": ["..."], "critic_approved": true }

Step 1 — Ensure a week exists

If $OMPB_HOME/plan-week.json is missing or stale (wrong week), generate it:

It comes from the periodized plan. If there's no plan-state.json/goal.json, route to /pb-plan first.
Otherwise delegate to oh-my-personal-best:session-coach to prescribe the 7 days for the current plan-state.json phase/target (paces derived from runner-profile.json PBs), and have the orchestrator write $OMPB_HOME/plan-week.json in the contract above. Respect the safety gate — if physio-advisor has an active YELLOW/RED, the week must reflect it.

Read the full file on GitHub · 65 lines

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.

12d ago First seen · 65 lines · 16 tokens per session scan A f29b61fd364c

Subscribe to this mod's changes

pb-week is a skill published in the GitHub repository seungwee-choi/oh-my-personal-best (3 stars, last pushed 12d ago), licensed MIT. It adds 16 tokens to every session and 811 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.

Claude Code Multi-Agent Scientific ai-agents claude-code-plugin marathon running

relax-dev-debug

Develop and debug the Relax reinforcement learning project. Use this skill whenever modifying code in the relax/ directory, or running remote training jobs on a Ray cluster for validation. Also use it when the user mentions training, debugging training runs, submitting Ray jobs, or fixing training errors.

redai-infra/Relax · 60 tokens

great_cto

Use when the CTO describes a feature, task, or project goal. Orchestrates the full SDLC pipeline automatically based on project type.

avelikiy/great_cto · 32 tokens

local-paper-navigator

Find and read papers from the local papers library (repo papers/, mounted at /papers/). Three native tools form a reading funnel: papersearch (one line per paper), paperread (card + section outline), papersection (one verbatim section — the only full-text access). Use when: find papers in the local library, read a…

CamusGIT/EvoQuant · 119 tokens

anti-patterns

Catalogue of known SDLC anti-patterns that greatcto agents must actively reject when reviewing architecture, plans, code, or post-mortems. Used by architect (pre-impl), pm (planning), senior-dev (impl), l3-support (post-incident).

avelikiy/great_cto · 59 tokens

cost-model

Standardized cost-estimation framework for greatcto plans. Forces explicit LLM cost, infra cost, human-supervision time, and the (defensible) human-equivalent comparison. Output format is parsable by the board's /api/cost path — must follow exactly.