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-injury)<a href="https://agentmods.dev/skills/seungwee-choi/oh-my-personal-best/pb-injury"><img src="https://agentmods.dev/badge/skills/seungwee-choi/oh-my-personal-best/pb-injury/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-injury"><img src="https://agentmods.dev/badge/skills/seungwee-choi/oh-my-personal-best/pb-injury.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.00025 | $0.00867 |
| Opus 5 | $0.00013 | $0.00434 |
| Sonnet 5 | $0.00005 | $0.00173 |
| Haiku 4.5 | $0.00003 | $0.00087 |
Grade A, and why
pb-injury 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<Use_When>
- The runner reports pain/injury: "무릎이 아파", "achilles is sore", "16km 뛰고 종아리 땡겨"
- A recovery check-in: "오늘 5km 뛰었는데 통증 없었어", "어제보다 나아졌어"
- "복귀 어떻게 해?", "다시 뛰어도 돼?", "내 부상 상태" </Use_When>
<Do_Not_Use_When>
- A RED-flag symptom (chest pain, dizziness, "something popped", numbness) → physio-advisor escalates to "seek medical care now"; this is not a substitute for medical evaluation. </Do_Not_Use_When>
Step 1 — Triage first (safety gate)
physio-advisor issues a GREEN/YELLOW/RED verdict. RED → stop, seek care; no episode/plan changes until cleared. Transient DOMS (GREEN) → no episode; reassure and continue.
Step 2 — Capture the episode (propose → confirm)
For a genuine injury, parse the report:
python3 "$CLAUDE_PLUGIN_ROOT/scripts/injury.py" parse "<the runner's words>"
Read the proposal back to the runner to CONFIRM (part / side / severity / onset). Only on confirm:
python3 "$CLAUDE_PLUGIN_ROOT/scripts/injury.py" create --part <knee|achilles|…> [--side left|right|both] [--severity N] [--onset YYYY-MM-DD]
The starting return-to-run phase is chosen conservatively from severity.
Step 3 — Stage the return (the ladder)
Explain the phase (rest → walk → walk_run → easy_only → build → full), what it permits, and the rule to advance (two consecutive pain-free, pain ≤ 2 running check-ins) or step back (a flare, pain ≥ 6). Record check-ins so the deterministic ladder — not motivation — decides progress:
python3 "$CLAUDE_PLUGIN_ROOT/scripts/injury.py" checkin --id <inj-id> [--ran] [--pain-during N] [--pain-after N]
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 · 75 lines · 25 tokens per session scan A 535f931a663a
pb-injury is a skill published in the GitHub repository seungwee-choi/oh-my-personal-best (3 stars, last pushed 12d ago), licensed MIT. It adds 25 tokens to every session and 867 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
great_cto
Use when the CTO describes a feature, task, or project goal. Orchestrates the full SDLC pipeline automatically based on project type.
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.
migration-ready-schema
Data-model rules that make a schema importable from day one, so the migration-import-engineer is never blocked on missing columns. Every SMB Product-Builder product must let a customer bring their data from an incumbent (ServiceTitan/Toast/Mindbody/Shopify) — that requires provenance (sourceref) and rollback…
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…
vertical-construction
Domain knowledge for the construction vertical (contractors, field crews) so architect and pm don't spec construction products naively. Covers the vocabulary (bid vs estimate, takeoff, retainage, change order, AIA G702/G703, lien waiver, draw schedule), the non-obvious money rules that incumbents like Procore price…