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 mkupermann/throughline --skill release-notesgit clone --depth 1 https://github.com/mkupermann/throughlineWrote 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/mkupermann/throughline/release-notes)<a href="https://agentmods.dev/skills/mkupermann/throughline/release-notes"><img src="https://agentmods.dev/badge/skills/mkupermann/throughline/release-notes/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/mkupermann/throughline/release-notes"><img src="https://agentmods.dev/badge/skills/mkupermann/throughline/release-notes.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.00012 | $0.00116 |
| Opus 5.5 | $0.00005 | $0.00046 |
| Sonnet 5.5 | $0.00002 | $0.00023 |
| Haiku 4.5 | $0.00001 | $0.00012 |
Grade A, and why
release-notes 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 today.
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 Notes
Gather merged pull requests since the last tag.
Group them by type: features, fixes, breaking changes.
Write one bullet per pull request with its title and number.
Link each bullet to the pull request URL.
Highlight breaking changes in a separate section at the top.
Keep the tone concise and factual.
Do not include internal refactors unless they affect users.
End with a contributors section listing pull request authors.
Save the draft to the repository root as RELEASE_NOTES.md.
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.
- today First seen · 25 lines · 12 tokens per session scan A 8ed8d437e927
release-notes is a skill published in the GitHub repository mkupermann/throughline (2 stars, last pushed today), licensed Apache-2.0. It adds 12 tokens to every session and 116 once invoked, about $0.0000 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-10-29.
Other skills, from other repositories
publish-site
Versioned site deploys to GitHub/Cloudflare/Netlify Pages.
version-bump
Automated semantic versioning and release workflow for Claude Code plugins. Handles version increments across package.json, marketplace.json, plugin.json manifests, build verification, git tagging, GitHub releases, and changelog generation. npm publishing is done by the tag-triggered GitHub Actions workflow through…
childhood
Babysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.
github
GitHub via gh CLI: PRs, issues, reviews, repos, auth.
build-and-release
Fully automate building and releasing a coding task.
release
Fully automate a release with version-bump and childhood.