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 CiscoDevNet/essentials --skill summarize-change-loggit clone --depth 1 https://github.com/CiscoDevNet/essentialsWrote 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/ciscodevnet/essentials/summarize-change-log)<a href="https://agentmods.dev/skills/ciscodevnet/essentials/summarize-change-log"><img src="https://agentmods.dev/badge/skills/ciscodevnet/essentials/summarize-change-log/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/ciscodevnet/essentials/summarize-change-log"><img src="https://agentmods.dev/badge/skills/ciscodevnet/essentials/summarize-change-log.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.00070 | $0.00749 |
| Opus 5.5 | $0.00028 | $0.00300 |
| Sonnet 5.5 | $0.00014 | $0.00150 |
| Haiku 4.5 | $0.00007 | $0.00075 |
Grade A, and why
summarize-change-log 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 1mo 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Summarize Change Log
Turn a long git log, squash message draft, or PR narrative into 1–5 copy-paste markdown bullets for a GitHub merge commit or extended description.
Output format
Return only markdown bullets. No preamble, no section headings unless the user asks.
- **type(scope): subject** — One sentence: what changed and why it matters.
- 1 to 5 bullets, never more than 5.
- Preserve
Co-authored-by:footers from the input only if present; place after bullets with a blank line before them.
Subject rules
Follow Conventional Commits 1.0.0:
- Format:
<type>[optional scope]: <description>— imperative mood, lowercase type. - Types:
feat,fix,docs,refactor,perf,test,build,ci,chore. - Entire subject ≤ 50 characters (type, scope, colon, space, description).
- Scope matches the primary area (
langsmith-client,azure-ai,hello-agent).
What changed, not process
Every subject must state what changed. Ban vague/process subjects:
| Bad | Good |
|---|---|
address PR #513 review comments |
fix(langsmith-client): defer delete confirm |
port docs from #510 |
docs(langsmith-client): document --deployment |
follow up on review |
fix(hello-agent): align listener id messaging |
Consolidation (>5 input commits)
- Group by scope + intent; merge overlapping fixes.
- Keep distinct areas separate (infra vs CLI vs docs).
- If still >5, drop least user-visible items; fold detail into a bullet body.
Validation (required)
Before returning output, run from this skill's directory:
scripts/validate-summary.sh /tmp/draft-summary.md
Or validate the checked-in fixture:
scripts/validate-summary.sh \
examples-good.md
Or pipe stdin:
printf '%s\n' '- **fix: short subject** — Details.' \
| scripts/validate-summary.sh
The script enforces:
- 1–5 bullets in the expected format
uv run cz check -m … -l 50(explicit 50-char limit; config alone is not applied without-l)- Vague-subject blocklist
What ships with it
6 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.
- 1mo ago First seen · 92 lines · 70 tokens per session scan A 812b53f7209a
summarize-change-log is a skill published in the GitHub repository CiscoDevNet/essentials (7 stars, last pushed 17d ago), licensed Apache-2.0. It adds 70 tokens to every session and 749 once invoked, about $0.0003 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-09-04.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
review-triage-phase
Produces canonical review actions from fetched review state and renders action markdown. Use when the user wants only triage/action-planning for the review-framework workflow.
multiline-commit-messages
Use single-quoted strings for multiline git commit messages in the Shell tool. Prevents heredoc escaping failures that produce garbled commit messages.
git-ops
Close out a local coding task on the bound daemon — stage, commit, branch, merge, push via cloud git — and when a merge conflicts, STOP and escalate with the file list instead of auto-resolving. Push reaches only the bare replica; prod-triggering tags are refused.
hero-diff-highlight
A dark code editor reveals a red deletion then a green addition with a soft pulse. Function: PR / code-change explainer.