Borrowing it
Nothing to install: this file belongs to loqwai/paper-cranes. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/loqwai/paper-cranes/main/.claude/skills/changelog/SKILL.mdgit clone --depth 1 https://github.com/loqwai/paper-cranesWrote 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/loqwai/paper-cranes/changelog)<a href="https://agentmods.dev/skills/loqwai/paper-cranes/changelog"><img src="https://agentmods.dev/badge/skills/loqwai/paper-cranes/changelog/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/loqwai/paper-cranes/changelog"><img src="https://agentmods.dev/badge/skills/loqwai/paper-cranes/changelog.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.00028 | $0.00824 |
| Opus 5.5 | $0.00011 | $0.00330 |
| Sonnet 5.5 | $0.00006 | $0.00165 |
| Haiku 4.5 | $0.00003 | $0.00082 |
Grade A, and why
changelog 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 11d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate Changelog
Update docs/CHANGELOG.md, README.md, and supporting docs with new features since the last changelog commit.
Context
Current changelog:
!cat docs/CHANGELOG.md 2>/dev/null || echo "(no changelog yet)"
Current README "What's New" section:
!sed -n '/## What.s New/,/^## /p' README.md 2>/dev/null | head -30 || echo "(no What's New section yet)"
Last changelog commit:
!git log -1 --format="%H %as" -- docs/CHANGELOG.md 2>/dev/null || echo "(never committed)"
Commits since last changelog update (excluding shaders and images):
!git log $(git log -1 --format="%H" -- docs/CHANGELOG.md 2>/dev/null || echo "HEAD~50")..HEAD --no-merges --format="%h|%as|%s" -- ':!shaders' ':!public/images' ':!*.png' ':!*.jpg' ':!*.webp' ':!*.gif'
Recent merges (for PR numbers):
!git log $(git log -1 --format="%H" -- docs/CHANGELOG.md 2>/dev/null || echo "HEAD~50")..HEAD --merges --oneline | head -20
Existing feature docs:
!ls docs/*.md 2>/dev/null
When invoked directly (/changelog)
-
Only add what's new: Compare the commits above against what's already in the changelog. Skip anything already documented.
-
Focus on what a user would be excited about: New capabilities, meaningful UX improvements, and important fixes. Skip internal refactors, doc typos, CI tweaks, and code cleanup unless they change user-facing behavior.
-
Categorize into: Features, Fixes, or Developer Experience.
-
Write concise entries: Bold the feature name, dash, one-sentence description. Include PR numbers as GitHub links when available (e.g.
[#98](https://github.com/loqwai/paper-cranes/pull/98)). -
Link to feature docs: If a dedicated doc exists in
docs/, link the entry to it. If a new feature is significant enough to warrant its own doc, create one — keep it lean (under 60 lines), focusing on non-obvious details. -
Update README.md: Keep the "What's New" section near the top with the 3-5 most recent major features. This should read like highlights, not a full log — link to the changelog for the rest. Also update the Documentation table and "Fun developer features" bullets if new docs were created.
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.
- 11d ago First seen · 58 lines · 28 tokens per session scan A 99ddc48f148b
changelog is a skill published in the GitHub repository loqwai/paper-cranes (7 stars, last pushed 3d ago), licensed BSD-3-Clause. It adds 28 tokens to every session and 824 once invoked, about $0.0001 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-02.
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.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
repo-sync
Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…
git-commit-writer
Trigger when the user asks to write a commit message, generate a commit from staged changes, review a diff before committing, or says "/commit". Reads git diff --staged and produces an opinionated, convention-matching commit message.