Borrowing it
Nothing to install: this file belongs to sportsdataverse/sportsdataverse-js. 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/sportsdataverse/sportsdataverse-js/main/.github/copilot-instructions.mdgit clone --depth 1 https://github.com/sportsdataverse/sportsdataverse-jsWrote 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/sportsdataverse/sportsdataverse-js/copilot-instructions)<a href="https://agentmods.dev/instructions/sportsdataverse/sportsdataverse-js/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/sportsdataverse/sportsdataverse-js/copilot-instructions.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.1 | $0.01238 | $0.01238 |
| Opus 5 | $0.00619 | $0.00619 |
| Sonnet 5 | $0.00248 | $0.00248 |
| Haiku 4.5 | $0.00124 | $0.00124 |
Grade A, and why
sportsdataverse-js copilot-instructions.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 8d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Copilot instructions — sportsdataverse (Node.js)
A TypeScript, ESM-only Node.js client (Node ≥ 20.18.1) for sports data: a cross-league ESPN surface plus native (non-ESPN) live-API families and seven cross-sport provider families, all with a tidy parser layer.
Architecture (how the code is generated)
- Codegen-driven.
tools/codegen/generate.mjsreads the endpoint YAML intools/codegen/endpoints/*.yaml(the single source of truth) and generates the runtime wrapper tables undersrc/generated/, the per-league reference docs underdocs/docs/reference/, and the playground metadatadocs/src/playground/endpoints.json. - Do NOT hand-edit generated output (
src/generated/**,docs/docs/reference/**,docs/src/playground/endpoints.json). Edit the YAML (or the codegen templates) and runnpm run codegen.npm run codegen:checkis the drift gate — it must stay green (CI fails otherwise). - New non-ESPN families come from a canonical OpenAPI spec via
tools/codegen/from-openapi.mjs(OpenAPI 3.x → endpoint-YAML skeleton). - The sport-grouped reference sidebar is codegen-owned — never hand-edit it.
docs/src/generated/reference-sidebar.js(anddocs/sidebars.js) group league reference docs bysport. To regroup, edittools/codegen/endpoints/leagues.yamlorgenerate.mjsand runnpm run codegen— the file is drift-guarded bynpm run codegen:check.
Conventions
- ESM only —
import sdv from 'sportsdataverse'. There is no CommonJSrequireexport. In RunKit/notebooks useawait import('sportsdataverse'). - Dual-case naming — every generated wrapper is exposed under BOTH snake_case
(
espn_nba_scoreboard,mlb_teams) and camelCase (espnNbaScoreboard,mlbTeams). Same function, either name. - Parser contract — parsers are
(raw: any) => Record<string, any>[]: return a tidy array of flat (snake_cased, nested-flattened) row objects; return[]on empty/malformed input; never throw.{ parsed: true }is strictly additive (omitting it returns the raw payload). When you changesrc/parsers/**, re-runnpm run bundle:parsers(the playground bundle) so its staleness test passes. - Flat-API getter runtimes. The flat dispatch defaults to the shared JSON-only
no-auth getter (
src/core/client.ts). A family needing non-JSON bodies or custom request shaping registers its own getter inGETTER_OVERRIDES(src/leagues/_make_flat.ts) keyed byapistem:- HockeyTech / LeagueStat (
sdv.hockeytech.*,src/core/hockeytech_runtime.ts) — JSONP family; the getter strips theangular.callbacks._N({…})wrapper beforeJSON.parse, usestab=(notview=) on thegcfeed, applies a PWHL play-by-play key override, and injects each league'sclient_code/key/site_idfrom a per-league registry (PWHL + AHL/OHL/WHL/QMJHL;SDV_<LEAGUE>_API_KEYoverrides the key). QMJHL uses a second host (cluster.leaguestat.com). - BartTorvik / T-Rank (
sdv.torvik.*,src/core/torvik_runtime.ts) — sends a browser-like User-Agent (barttorvik rejects default UAs) and returns the raw body so each parser branches on format (CSV via papaparse, orJSON.parseof headerless positional column arrays ported from hoopR). Both are standalone provider namespaces (sdv.<ns>.*, not leagues).
- HockeyTech / LeagueStat (
- Docs guides + live runner. Getting-started guides are
.mdxunderdocs/docs/guides/;<RunCell>(docs/src/components/RunCell) is embeddable inline in any guide for a live single-endpoint Run (via the/api/runproxy). After changingsrc/parsers/**(and re-bundling) or the example manifesttools/docs/examples.mjs, runnpm run docs:examplesto refresh the frozen tables and keepnpm run docs:examples:checkgreen (a CI gate). The homepage + reference sidebar are data-driven/codegen-owned — don't hand-edit them. - New modules must be typed and pass
npm run typecheck(tsc) +npm run build. - Tests are Mocha, no network (inline payloads / committed fixtures);
live/integration tests are gated behind
SDV_LIVE=1.
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.
- 8d ago First seen · 72 lines · 1,238 tokens per session scan A 70c7abe35d0c
sportsdataverse-js copilot-instructions.md is an instructions file published in the GitHub repository sportsdataverse/sportsdataverse-js (84 stars, last pushed 19d ago), licensed MIT. It adds 1,238 tokens to every session, about $0.0062 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-30.
Other instructions, from other repositories
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.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
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.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.