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 agentmods add skills/puckapi/claude-sports-analytics/dispatchnpx skills add PuckAPI/claude-sports-analytics --skill dispatchgit clone --depth 1 https://github.com/PuckAPI/claude-sports-analyticsWrote 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/puckapi/claude-sports-analytics/dispatch)<a href="https://agentmods.dev/skills/puckapi/claude-sports-analytics/dispatch"><img src="https://agentmods.dev/badge/skills/puckapi/claude-sports-analytics/dispatch.svg" alt="Measured on agentmods" 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 | $0.00059 | $0.01965 |
| Opus 5 | $0.00030 | $0.00983 |
| Sonnet 5 | $0.00012 | $0.00393 |
| Haiku 4.5 | $0.00006 | $0.00197 |
Grade A, and why
dispatch 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 3d 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Dispatch Guide
When a hockey analytics request comes in, match it to a pattern below. Load those skills. Don't load everything.
Default data tool: puckapi-tool -- covers most data needs. Load it alongside the relevant strategy skill unless the request specifically needs a different tool.
First-Use Persona Detection
On first interaction, identify which path the user is on:
| Signal | Persona | Start With |
|---|---|---|
| "What games are tonight?" / exploring data | Explorer | game-lookup + puckapi-tool |
| "Help me build a model" / "I want to predict" | Builder | hockey-analytics + feature-engineering |
| "What are tonight's best bets?" / "Give me picks" | Daily User | daily-card + odds-explorer |
| "I have a model, is it any good?" | Validator | walk-forward-validation + probability-calibration |
| "I'm new to hockey analytics" | Learner | hockey-analytics + ai-hockey-workflow |
| "I'm new to betting" | New Bettor | odds-analysis + edge-detection |
Request Patterns -> Skills to Load
"Who plays tonight?" / "What's the schedule?" / "Game results"
game-lookup-- find games by date, team, seasonpuckapi-tool--get_games,get_scheduleendpoints
"How are the Sabres doing?" / "Standings" / "Team stats"
team-analysis-- standings, stats, rankings, SOSpuckapi-tool--get_standings,get_team_stats
"Tell me about Connor McDavid" / "Player stats" / "Compare players"
player-scouting-- search, stats, comparison, NHLepuckapi-tool--search_players,get_player_stats
"Who's starting in goal?" / "Goalie matchup" / "Save percentage"
goalie-analysis-- leaderboard, workload, xG-adjusted metricspuckapi-tool--get_goalie_stats
"What are the odds?" / "Line shopping" / "Best price"
odds-explorer-- multi-book comparison, line movementpuckapi-tool--get_odds,get_line_movement- For odds math/devigging: also load
odds-analysis
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.
- 3d ago First seen · 161 lines · 59 tokens per session scan A 25f4564670bc
dispatch is a skill published in the GitHub repository PuckAPI/claude-sports-analytics (2 stars, last pushed 3mo ago), licensed MIT. It adds 59 tokens to every session and 1,965 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
a11y-analyzer
Accessibility analysis from session data — keyboard-only navigation patterns, focus order issues, screen reader compatibility, and accessibility regressions. Use when auditing a11y compliance, investigating accessibility bugs, or validating inclusive design.
campaign-tracker
Track marketing campaign performance — UTM-tagged traffic, landing page conversion, campaign cohort behavior, and ROI signals. Use when analyzing campaign performance, measuring landing page effectiveness, or comparing marketing channels.
changelog-detective
Detect what changed in the product by comparing before and after a deploy or date — find new behaviors, new errors, changed user flows, and unexpected side effects that weren't in the release notes. Use after a deploy or when the user suspects something changed but doesn't know what.
form-analyzer
Form field-level analysis — abandonment by field, validation errors, time-to-complete, and which fields cause users to leave. Use when investigating form performance, signup drop-off, or checkout form friction.
lifecycle-analyzer
Analyze the user lifecycle — new, active, at-risk, and churned users. Use when understanding user progression, identifying at-risk users, or measuring lifecycle conversion rates.
scroll-depth-analyzer
Analyze how far users scroll on key pages — content visibility, where users stop reading, and whether important content is being seen. Use when evaluating page layout, content effectiveness, or CTA placement.