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/parthakker/nfl-analytics/releasenpx skills add parthakker/nfl-analytics --skill releasegit clone --depth 1 https://github.com/parthakker/nfl-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/parthakker/nfl-analytics/release)<a href="https://agentmods.dev/skills/parthakker/nfl-analytics/release"><img src="https://agentmods.dev/badge/skills/parthakker/nfl-analytics/release.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.00017 | $0.00226 |
| Opus 5 | $0.00009 | $0.00113 |
| Sonnet 5 | $0.00003 | $0.00045 |
| Haiku 4.5 | $0.00002 | $0.00023 |
Grade A, and why
release 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.
What it actually says
Release ritual
python -m ruff check .andpython -m pytest tests/unit -q— both green.- If web/ui/src changed:
cd web/ui && npm run build(includes tsc). - If scripts/ or src/nfl_analytics changed:
python -m pytest -m warehouse -q. - If any API endpoint changed: confirm smoke CHECK + tests/api coverage exist.
- Docs honesty pass: does CLAUDE.md / README / the relevant docs/dictionary page still tell the truth about what changed? Fix drift now.
- Commit: conventional prefix (feat/fix/chore/test/docs/ci), imperative
subject, body listing the what+why. NEVER commit *.duckdb files or data/
(except the three curated JSONs).
git statusmust be clean after. - Push only when Parth asked for a push.
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 · 19 lines · 17 tokens per session scan A de4f27a2f195
release is a skill published in the GitHub repository parthakker/nfl-analytics (0 stars, last pushed 3d ago), licensed MIT. It adds 17 tokens to every session and 226 once invoked, about $0.0001 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
understanding-streamlit-architecture
Explains Streamlit's internal architecture including backend runtime, frontend rendering, and WebSocket communication. Use when debugging cross-layer issues, understanding how features work end-to-end, planning architectural changes, or onboarding to the codebase. Covers ForwardMsg/BackMsg protocol, script rerun…
debugging-streamlit
Debug Streamlit frontend and backend changes using make debug with hot-reload. Use when testing code changes, investigating bugs, checking UI behavior, or needing screenshots of the running app.
fixing-flaky-e2e-tests
Diagnose and fix flaky Playwright e2e tests. Use when tests fail intermittently, show timeout errors, have snapshot mismatches, or exhibit browser-specific failures.
fixing-streamlit-ci
Analyze and fix failed GitHub Actions CI jobs for the current branch/PR. Use when CI checks fail, PR checks show failures, or you need to diagnose lint/type/test errors and verify fixes locally.
updating-internal-docs
Review internal documentation (.md files) against the current codebase state and propose updates for outdated or incorrect information.
assessing-external-test-risk
Assesses whether branch or PR changes are high-risk for externally hosted or embedded Streamlit usage and recommends whether external e2e coverage with @pytest.mark.externaltest is needed. Use during code review, PR triage, or test planning when changes touch routing, auth, websocket/session behavior, embedding…