Borrowing it
Nothing to install: this file belongs to PuckAPI/claude-sports-analytics. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/PuckAPI/claude-sports-analytics/main/CLAUDE.mdgit 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/instructions/puckapi/claude-sports-analytics/claude-md)<a href="https://agentmods.dev/instructions/puckapi/claude-sports-analytics/claude-md"><img src="https://agentmods.dev/badge/instructions/puckapi/claude-sports-analytics/claude-md/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/instructions/puckapi/claude-sports-analytics/claude-md"><img src="https://agentmods.dev/badge/instructions/puckapi/claude-sports-analytics/claude-md.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.00640 | $0.00640 |
| Opus 5.5 | $0.00256 | $0.00256 |
| Sonnet 5.5 | $0.00128 | $0.00128 |
| Haiku 4.5 | $0.00064 | $0.00064 |
Grade A, and why
claude-sports-analytics CLAUDE.md 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 1mo 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.
Hockey Skills -- Claude Code Instructions
Public Repo Rules
This is a public, open-source repository. Every commit, file, and message is visible to anyone.
Never include:
- AI attribution or co-author lines in commits, code, or comments
- Personal information (names, emails, addresses, usernames beyond the org)
- API keys, secrets, tokens, or credentials (even expired ones)
- Internal URLs, private repo paths, or filesystem paths (e.g., /Users/*)
- References to private repos, internal tools, or business strategy
- Revenue numbers, pricing strategy discussions, or customer data
- References to other projects (PuckCast, OWSH, brain vault, etc.)
Commit messages:
- Written as if by the project maintainer, not an AI
- Describe the what and why, no "Generated by" or "Co-Authored-By" lines
- Keep them concise and professional
Code and content:
- No "AI-powered", "intelligent", or similar buzzwords
- No comments referencing internal conversations or decisions
- Skill descriptions should be factual and specific to what the skill does
- Credit costs must match the live PuckAPI pricing (see puckapi-tool/endpoints.md)
Repo Structure
claude-sports-analytics/
├── .claude-plugin/plugin.json # Plugin manifest
├── skills/ # 28 skill directories
│ ├── puckapi-tool/ # MCP tool reference (endpoints + fields)
│ ├── hockey-analytics/ # Core metrics and concepts
│ ├── game-lookup/ # Finding and filtering games
│ └── ... # See README for full list
└── docs/ # Glossaries, routing, season logic
Key Facts
- 28 skills, all NHL/hockey focused
- MCP server at mcp.puckapi.com/mcp
- Data starts from the 2010-11 season. 16 completed seasons plus the one in progress. Do not claim 2008-09; it is not there
- 32 active NHL teams (includes Utah Hockey Club, not Arizona Coyotes)
- Odds from the books PuckAPI tracks (DraftKings, FanDuel, BetMGM, ESPN BET and others). The count moves as books come and go, so do not publish a number.
- 15 MCP tools with credit costs defined in puckapi-tool/endpoints.md
- Shot-quality metrics are returned by the API, not computed by the caller:
gsax,expectedGoalsAgainst,highDangerSavePct,rollingSavePct,rollingGsax,trend,restDayson goalies;corsiPct,fenwickPct,expectedGoalsFor,expectedGoalsAgainston teams;goalie_startswith time on ice onget_game_detail - Team possession is 5v5 by convention, goalie expected goals cover every strength. Never difference the two
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.
- 1mo ago Changed · +8 lines · +160 tokens per session e26ac2406c45
- 1mo ago First seen · 48 lines · 480 tokens per session scan A 0f248570dbfc
claude-sports-analytics CLAUDE.md is an instructions file published in the GitHub repository PuckAPI/claude-sports-analytics (3 stars, last pushed 8d ago), licensed MIT. It adds 640 tokens to every session, about $0.0026 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.