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-insights)<a href="https://agentmods.dev/skills/seungwee-choi/oh-my-personal-best/pb-insights"><img src="https://agentmods.dev/badge/skills/seungwee-choi/oh-my-personal-best/pb-insights/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-insights"><img src="https://agentmods.dev/badge/skills/seungwee-choi/oh-my-personal-best/pb-insights.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.00029 | $0.00700 |
| Opus 5.5 | $0.00012 | $0.00280 |
| Sonnet 5.5 | $0.00006 | $0.00140 |
| Haiku 4.5 | $0.00003 | $0.00070 |
Grade A, and why
pb-insights 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 2mo 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<Use_When>
- "내 하이라이트", "뭐 좋아졌어?", "요즘 어때?", "show my progress", "any wins lately?"
- After a sync/import, to celebrate genuine improvements and flag a hidden fatigue spike
- As a section of
/pb-report(the comprehensive report embeds the top insights) </Use_When>
<Do_Not_Use_When>
- Fewer than ~8 logged runs → not enough history for self-relative signals; route to
/pb-setupor encourage logging more first (detect returns[]). </Do_Not_Use_When>
Step 1 — Detect
python3 "$CLAUDE_PLUGIN_ROOT/scripts/insights.py" # ompb_core.detect_insights(home, deep=True)
Returns score-ranked cards: {id, kind (improvement|pr|warning|consistency|adaptation), icon, headline, wow (one-line meaning), stat, score, coach_hint}. deep=True lets zone/decoupling/lap
detectors pull signals from a few recent Strava runs (analyze_activity, ≤4 calls — bounded, never
bulk); deep=False for a fully offline pass.
Step 2 — Narrate the top few
Show the highest-scoring 3–5 cards. Lead with the headline number, then the one-line meaning. A
warning card (e.g. an acute:chronic load spike) is surfaced honestly — celebrate the wins AND
name the fatigue risk. Use the coach_hint as a seed for one sentence of "what to do with it".
Step 3 — (Optional) deepen
If the runner wants the "so what" for the goal, hand the top cards to race-analyst for one
grounded paragraph tying the trend to the limiter and the target race.
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.
- 2mo ago First seen · 59 lines · 29 tokens per session scan A b8d73a746e42
pb-insights is a skill published in the GitHub repository seungwee-choi/oh-my-personal-best (3 stars, last pushed 2mo ago), licensed MIT. It adds 29 tokens to every session and 700 once invoked, about $0.0001 per session on Opus 5.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.
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…
deploy-landed
A deployment verification procedure that checks whether the intended code revision is actually running, its environment settings are present, and the product works. A deployment is the process of putting new software on a server or hosting platform.
pm
Project manager for GitHub issues: brainstorm design approaches, create structured issues optimized for LLM agent teams, triage and recommend what to work on next, audit and clean up stale issues, or deep-validate a single issue against the codebase. Triggers: create issue, plan work, new task, project manager, write…