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/jcottam/agent-resources/commit-release-notesnpx skills add jcottam/agent-resources --skill commit-release-notesgit clone --depth 1 https://github.com/jcottam/agent-resourcesWhat 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.00067 | $0.01093 |
| Opus 5 | $0.00034 | $0.00547 |
| Sonnet 5 | $0.00013 | $0.00219 |
| Haiku 4.5 | $0.00007 | $0.00109 |
Grade A, and why
commit-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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit Release Notes
Turn git history into clear summaries for teammates, stakeholders, or changelogs — not developer jargon.
Workflow
1. Gather commits
Run read-only git commands. Do not commit, push, or edit files unless the user explicitly asks.
| User intent | Command |
|---|---|
| Recent work (default) | git log --oneline -10 |
| By author | git log --author=<name> --oneline -15 |
| Since a tag or commit | git log <ref>..HEAD --oneline |
| Detail per commit | git log --stat --format='%h %s%n%b' <range> |
Defaults when unspecified:
- Branch: current branch
- Count: 5–15 commits, enough to cover the work without noise
- Skip empty merge commits unless they carry meaningful context
2. Understand the changes
- Read commit messages and file stats (
--stat) to learn what actually changed. - Group related commits into one user-facing idea (e.g. three truncation commits → "prompts load without flicker").
- Focus on user-visible behavior: what someone using the app will see or feel.
- Deprioritize internal-only work (refactors, lockfile-only bumps) unless it is the whole story or the user asked for technical detail.
3. Deliver outputs (in order)
Produce only what the user asked for. When they want the full treatment, use this order:
- Technical digest (optional) — one short paragraph for engineers; file names and mechanisms OK here.
- Plain paragraph — 3–5 sentences at the requested reading level (default: 8th grade).
- Bulleted list — same content as the paragraph, one idea per line.
If the user liked the paragraph and asks for bullets next, convert without re-explaining from scratch.
Plain-language writing rules
- Short sentences. Common words. Active voice.
- Describe what changed for the user, not which files moved.
- Prefer: "the page loads smoother", "videos show first", "a duplicate button was removed".
- Avoid unless requested: refactor, dependency bump, ResizeObserver, hook names, component paths.
- No hype ("exciting", "powerful", "game-changing"). State facts.
- Dependency updates: one line like "software packages were updated" unless versions matter to the audience.
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 · 120 lines · 67 tokens per session scan A b119c02ccc27
commit-release-notes is a skill published in the GitHub repository jcottam/agent-resources (30 stars, last pushed 26d ago), licensed MIT. It adds 67 tokens to every session and 1,093 once invoked, about $0.0003 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 skills, from other repositories
workers-best-practices
Reviews and authors Cloudflare Workers code against production best practices. Load when writing new Workers, reviewing Worker code, configuring wrangler.jsonc, or checking for common Workers anti-patterns (streaming, floating promises, global state, secrets, bindings, observability). Biases towards retrieval from…
find-journalists
Build, refine, dedupe, and enrich small fit-checked journalist lists for newsjack campaigns. Uses the newsjack CLI (preferred) or the medialyst MCP for news search and journalist enrichment, and falls back to a best-effort local mode with no verified contacts; the agent owns how returned data is organized.
story-origin-check
Recover the first public timestamp and canonical major coverage for a newsjacking signal, then decide whether newer coverage is the same story, a different story, or a materially new development.
annotating-task-lineage
Annotate Airflow tasks with data lineage using inlets and outlets. Use when the user wants to add lineage metadata to tasks, specify input/output datasets, or enable lineage tracking for operators without built-in OpenLineage extraction.
prompt-proximity-architecture
Turn an approved measurement charter, ICPs, and buyer jobs into a budget-aware prompt coverage blueprint across proximity bands, aided status, information acts, journey states, roles, locales, evidence grades, partitions, and measurement lanes. Use before prompt wording to define required, optional, and prohibited…
relevance-coarse-filter
Cheap, high-recall first-pass filter that removes obvious junk from a detector candidate pool before expensive story-origin research and PR judgment. Decides keep, monitoronly, or reject — never ranks, writes angles, verifies dates, or decides whether to pitch.