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.
/plugin marketplace add seungwee-choi/oh-my-personal-best/plugin install oh-my-personal-bestWrote 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/seungwee-choi/oh-my-personal-best/pb-body)<a href="https://agentmods.dev/skills/seungwee-choi/oh-my-personal-best/pb-body"><img src="https://agentmods.dev/badge/skills/seungwee-choi/oh-my-personal-best/pb-body/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/seungwee-choi/oh-my-personal-best/pb-body"><img src="https://agentmods.dev/badge/skills/seungwee-choi/oh-my-personal-best/pb-body.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.00021 | $0.00603 |
| Opus 5 | $0.00010 | $0.00302 |
| Sonnet 5 | $0.00004 | $0.00121 |
| Haiku 4.5 | $0.00002 | $0.00060 |
Grade A, and why
pb-body 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.
How it starts
The opening of the file, as written. The whole thing — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<Use_When>
- "오늘 체중 62.5", "weighed in at 62.5kg", weight check-ins
- "레이스 체중 목표 60", "race weight", fueling for weight management
- "요즘 살 빠지는데 괜찮아?", "왜 페이스가 안 나오지" (possible under-fueling) </Use_When>
<Do_Not_Use_When>
- Signs of disordered eating, a clinical dietary condition, or rapid unexplained loss → fuel-advisor states the coaching boundary and refers to a registered dietitian / physician. Not a weight-loss app. </Do_Not_Use_When>
Step 1 — Log (if a weight was reported)
python3 "$CLAUDE_PLUGIN_ROOT/scripts/body.py" log --kg <float> [--bodyfat <float>] [--note "..."]
A race-weight goal: body.py set-target --kg <float> (merged into goal.json, never clobbering the race goal).
Step 2 — Read the trend
python3 "$CLAUDE_PLUGIN_ROOT/scripts/body.py" summary
Gives current weight, ma7/ma30, kg/week rate, race-weight gap, and the under-fueling flag.
Step 3 — Advise (fuel-advisor)
- If the loss rate exceeds ~1%/week of bodyweight, or the under-fueling flag is set → LEAD with that: reassess intake and recovery before any leanness framing. Too-fast loss costs muscle, immunity, and performance.
- Otherwise, ground daily/long-run/race fueling in the actual trend and the race-weight gap.
<Stop_Conditions>
$CLAUDE_PLUGIN_ROOTunset → runpython3 scripts/body.py …from the repo.- Too few logs for a trend → log the entry and report only the current value; don't infer a rate from one point. </Stop_Conditions>
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 · 56 lines · 21 tokens per session scan A 19fd2956e719
pb-body is a skill published in the GitHub repository seungwee-choi/oh-my-personal-best (3 stars, last pushed 12d ago), licensed MIT. It adds 21 tokens to every session and 603 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.
Other skills, from other repositories
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.
great_cto
Use when the CTO describes a feature, task, or project goal. Orchestrates the full SDLC pipeline automatically based on project type.
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…
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).
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.
stack-baseline
The pinned default technology stack for SMB Product-Builder products. One source of truth so the architect, app-scaffolder, auth-engineer, and senior-dev never re-decide the stack per build — they build ON it. Covers framework, ORM/DB, auth, UI, payments/email/SMS, files, jobs, testing, hosting, and observability…