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/corv89/shannot/changelognpx skills add corv89/shannot --skill changeloggit clone --depth 1 https://github.com/corv89/shannotWhat 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.00013 | $0.00601 |
| Opus 5 | $0.00006 | $0.00300 |
| Sonnet 5 | $0.00003 | $0.00120 |
| Haiku 4.5 | $0.00001 | $0.00060 |
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 yesterday.
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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/changelog - Generate Changelog Entry
Purpose
Generate a Keep a Changelog entry matching the existing CHANGELOG.md style, if available.
Usage
/changelog [version]
Version is optional — suggest one based on the changes (patch for fixes, minor for features, major for breaking changes).
Process
-
Find the last tag and get commits
git describe --tags --abbrev=0 git log --pretty=format:'%s' <tag>..HEAD -
Categorize using Keep a Changelog sections
### Features— new capabilities### Changed— breaking or notable behavior changes### Enhancements— improvements to existing features### Bug Fixes— things that were broken### Removed— removed features (rare)
-
Write entries in a consistent voice
Match the existing style:
- Start with imperative verb or noun phrase
- Bold key concepts on first mention:
**Overlay commit model for file writes**: - Sub-bullets for details when a feature has multiple parts
- Technical but accessible — users are developers
Examples:
Fix login regression: use OAuth2 instead of deprecated token flowImprove CLI help with quick start guide and clearer description**Remote file sync**: sync_remote() now supports conflict detection
-
Skip internal-only changes
Omit: CI tweaks, refactoring without user impact, dependency bumps (unless security-related)
-
Output format
## [x.y.z] - YYYY-MM-DD ### Features - **Feature name**: Description of what users can now do ### Bug Fixes - Fix specific thing that was broken -
Prepend to CHANGELOG.md
If CHANGELOG.md doesn't exist, create it with this header:
# Changelog All notable changes to this project will be documented in this file. The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
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.
- yesterday First seen · 91 lines · 13 tokens per session scan A 32ae458f7738
changelog is a skill published in the GitHub repository corv89/shannot (25 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 13 tokens to every session and 601 once invoked, about $0.0001 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-09-01.
Other skills, from other repositories
changelog-draft
Generate a reviewable changelog draft from PRs merged in a release range. Extracts explicit CHANGELOG markers, classifies unmarked PRs, adds external contributor attribution, and outputs markdown + JSON artifacts. Does NOT mutate channelversions.json.
classify-changelog-pr
Reference guidance for classifying whether an unmarked PR should appear in the changelog and under which category. Used inline by the changelog-draft skill — not dispatched as a separate agent.
promote-feature
Promote a feature-flagged feature to Dogfood, Preview, or Stable in the Warp codebase. Use when a feature behind a FeatureFlag is ready to roll out to a broader audience, including wiring up the compile-time/runtime bridge and deferring flag cleanup safely.
heinzel-fleet-audit
Compare key policies across all servers in memory/servers/ to surface silent drift. Makes no configuration changes; writes one audit-trail line to each host's journal. Probes unattended-upgrades, sshd effective config, firewall posture, MTA, time sync, and auto-reboot behaviour. Use when the user asks to "fleet…
heinzel-housekeeping
Run a heinzel housekeeping (health) inspection on a server — disk, memory, load, pending updates, firewall, SSL certs, failed systemd units, logs, kernel reboot status, and service-specific checks. Use when the user asks to "run housekeeping", "housekeeping report", "run a health check on ", or "do routine…
heinzel-security
Run a heinzel security audit on a server — SSH hardening (password auth, weak algos, root login), firewall, user account hygiene, listening services, kernel hardening (ASLR, IP forwarding), file permissions, SUID/SGID audit, fail2ban. Use when the user asks for a "security audit", "security review", "hardening check"…