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/sananthanarayan/skilldrop/release-notesnpx skills add sananthanarayan/skilldrop --skill release-notesgit clone --depth 1 https://github.com/sananthanarayan/skilldropWhat 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.00072 | $0.01282 |
| Opus 5 | $0.00036 | $0.00641 |
| Sonnet 5 | $0.00014 | $0.00256 |
| Haiku 4.5 | $0.00007 | $0.00128 |
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 2d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
release-notes
Converts commit history into two artifacts with different readers: customer-facing release notes (benefits, no commit-speak) and an internal changelog (Keep a Changelog format, every line traceable to a commit). The rule that drives everything: write for the reader who didn't make the change.
How to respond
-
Resolve the range. Default: last tag to HEAD (
git describe --tags --abbrev=0). If no tags exist, ask for a start ref or take the user's two refs. State the resolved range at the top of the output: "v1.4.0..HEAD, 37 commits, 2026-05-02 → 2026-06-10". -
Gather the raw material.
git log <range> --no-merges --pretty='%h|%s|%an|%ad' --date=shortfor the commit list;git log <range> --statonly when a subject line is too vague to classify. Where theghCLI is available and the repo uses PRs, prefer PR titles over commit subjects (gh pr list --state merged --search "merged:>={date}") — they're written closer to reader language. Don't requiregh; commits alone are enough. -
Classify every change into Keep-a-Changelog categories plus one local bucket:
- Added / Changed / Fixed / Deprecated / Removed / Security — reader-visible
- Internal — refactors, CI, deps, tests; appears in the internal changelog, never in customer notes
- Needs review — can't tell what it does from the commit; goes in a list for the user, never guessed into customer notes
-
Hoist breaking changes and migrations to the top of both artifacts, each with an Action required line. A breaking change buried under "Changed" is the cardinal failure of release notes. Detect via
BREAKING,!:conventional-commit markers, migration files, major dependency bumps, and removed public API — and say which signal triggered the flag. -
Rewrite, don't transcribe. Each customer-facing line states what the reader can now do or no longer suffers. ✅ "Fixed a crash when exporting reports with more than 10,000 rows" — ❌ "fix NPE in ReportExporter.flush()". Drop ticket numbers and author names from customer notes; keep both in the internal changelog with the short hash on every line.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 62 lines · 72 tokens per session scan A e6824ef53f02
release-notes is a skill published in the GitHub repository sananthanarayan/skilldrop (2 stars, last pushed 18d ago), licensed MIT. It adds 72 tokens to every session and 1,282 once invoked, about $0.0004 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
openlore-plan-refactor
Identify a high-priority refactoring target, assess its blast radius, and write .openlore/refactor-plan.md without changing code. Use when asked to plan or prioritize a refactor.
openlore-brainstorm
Transform a feature idea into an annotated story using a Domain Sketch or Constrained Option Tree. Use when asked to brainstorm, explore, or shape a feature before implementation.
openlore-debug
Debug with OpenLore structural context, an explicit root-cause hypothesis, and RED/GREEN verification. Use when a bug, failure, or regression needs diagnosis and repair.
openlore-execute-refactor
Apply a confirmed .openlore/refactor-plan.md with a test gate after each change. Use when asked to execute or continue an OpenLore refactoring plan.
openlore-analyze-codebase
Run a full static OpenLore analysis and summarize architecture, call graph, refactoring issues, and duplicate code. Use when asked to analyze, map, or assess a codebase without LLM inference.
team-repair
Re-index OKF v0.2 index.md/log.md files, derive CDR.md, rebuild .skills.json and AGENTS.md in team-ai-directives, migrate v0.1→v0.2 frontmatter, scan for rule conflicts, and verify directive freshness. Use when indexes are inconsistent, orphans are detected, after bulk changes, or for periodic team AI directives…