Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add bjornj12/golf-coach --skill trackman-stats-analysisgit clone --depth 1 https://github.com/bjornj12/golf-coachWrote 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/bjornj12/golf-coach/trackman-stats-analysis)<a href="https://agentmods.dev/skills/bjornj12/golf-coach/trackman-stats-analysis"><img src="https://agentmods.dev/badge/skills/bjornj12/golf-coach/trackman-stats-analysis/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/bjornj12/golf-coach/trackman-stats-analysis"><img src="https://agentmods.dev/badge/skills/bjornj12/golf-coach/trackman-stats-analysis.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.00067 | $0.00989 |
| Opus 5 | $0.00034 | $0.00495 |
| Sonnet 5 | $0.00013 | $0.00198 |
| Haiku 4.5 | $0.00007 | $0.00099 |
Grade A, and why
trackman-stats-analysis 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 11d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Trackman Stats Analysis
Pull the user's Trackman data via the MCP and produce an honest, specific
diagnosis of where they're losing strokes. This skill does NOT prescribe
drills — it hands a prioritized weakness list to the golf-coaching skill.
Inputs
Call the MCP tools (run auth first if needed):
trackman(action="profile")→ current handicap.trackman(action="sessions")→ recent practice + rounds (default: last 60–90 days).trackman(action="rounds")→ scorecards for scoring analysis.trackman(action="clubs")→ per-club gapping and dispersion.trackman(action="session", activity_id=...)→ shot-level detail where you need it.
Then call synthesize() for the cross-source, context-aware view — it aligns
these Trackman findings against any GameBook on-course findings by skill area
(Trackman is clean-room/flat-lie; GameBook is on-course, real conditions), so a
gap that shows up in both isn't double-counted and one that only shows up
on-course points at lies/pressure/course-management rather than pure mechanics.
Diagnose from the aligned view where it's available, falling back to raw
trackman output when synthesize has nothing (e.g. no GameBook rounds saved).
If a tool errors with auth expired, re-run auth. If the MCP isn't
built yet (Phase 0/1 incomplete), say so and stop — don't invent numbers.
What to analyze
Work through these lenses and keep only what the data supports:
- Club gapping. From
trackman(action="clubs"), list avg carry per club. Flag overlapping clubs (gaps < ~8–10 m between adjacent clubs) and big holes in the set (gaps > ~18–20 m). Gaps cost approach shots. - Dispersion / consistency. Per club, look at carry spread and side/left-right scatter. Wide side dispersion on scoring clubs (wedges, short irons) is high-value to fix. Note the tightest and loosest clubs.
- Launch quality. Spot inefficiencies: low smash factor (poor strike), spin too high/low for the club, launch + spin combos that kill carry. Driver especially: launch/spin vs an efficient window.
- Scoring trends (from rounds): fairways hit %, greens in regulation, putts/round, and where doubles+ come from (driving? approach? short game?). This anchors practice to what actually costs scores.
- Handicap movement. Is it trending up, flat, or down over the window? Tie it to the above.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 77 lines · 67 tokens per session scan A 55592ab06a49
trackman-stats-analysis is a skill published in the GitHub repository bjornj12/golf-coach (1 stars, last pushed 1mo ago), licensed MIT. It adds 67 tokens to every session and 989 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…