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 littlebearapps/pitchdocs --skill changeloggit clone --depth 1 https://github.com/littlebearapps/pitchdocsWrote 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/littlebearapps/pitchdocs/changelog)<a href="https://agentmods.dev/skills/littlebearapps/pitchdocs/changelog"><img src="https://agentmods.dev/badge/skills/littlebearapps/pitchdocs/changelog.svg" alt="Measured on agentmods" 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.00052 | $0.01706 |
| Opus 5 | $0.00026 | $0.00853 |
| Sonnet 5 | $0.00010 | $0.00341 |
| Haiku 4.5 | $0.00005 | $0.00171 |
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 8d 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Changelog Generator
Format: Keep a Changelog
Follow keepachangelog.com with marketing-friendly language.
# Changelog
All notable changes to this project are documented here.
The format is based on [Keep a Changelog](https://keepachangelog.com/),
and this project adheres to [Semantic Versioning](https://semver.org/).
## [Unreleased]
### Added
- You can now generate READMEs with marketing-friendly language (#42)
### Changed
- Changelog entries are now written in reader-centric language (#38)
### Fixed
- Badge URLs no longer break when the repo is transferred (#35)
## [1.2.0] - 2026-02-20
### Added
- New `/roadmap` command pulls data from GitHub Projects (#30)
- User-benefit language across all generated documents (#28)
### Changed
- Quickstart section now shows TypeScript examples by default (#27)
### Deprecated
- The `--format plain` flag will be removed in v2.0 — use `--format markdown` (#25)
### Security
- Dependencies updated to patch CVE-2026-1234 (#33)
[Unreleased]: https://github.com/org/repo/compare/v1.2.0...HEAD
[1.2.0]: https://github.com/org/repo/compare/v1.1.0...v1.2.0
Compare URL patterns by platform (load platform-profiles for full mapping):
- GitHub:
https://github.com/org/repo/compare/v1.1.0...v1.2.0 - GitLab:
https://gitlab.com/org/repo/-/compare/v1.1.0...v1.2.0 - Bitbucket:
https://bitbucket.org/org/repo/branches/compare/v1.2.0..v1.1.0(note: reversed order)
Categories (Keep a Changelog Standard)
| Category | When to Use | Conventional Commit Types |
|---|---|---|
| Added | New features for users | feat: |
| Changed | Changes to existing functionality | feat: (modifications), refactor: (user-visible) |
| Deprecated | Features that will be removed | feat: with deprecation |
| Removed | Features that were removed | feat: (breaking) |
| Fixed | Bug fixes | fix: |
| Security | Vulnerability patches | fix: with security label |
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.
- 8d ago First seen · 174 lines · 52 tokens per session scan A bec97e24bcf6
changelog is a skill published in the GitHub repository littlebearapps/pitchdocs (8 stars, last pushed 4mo ago), licensed MIT. It adds 52 tokens to every session and 1,706 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-31.
Other skills, from other repositories
han-release
Cut a Han release: update CHANGELOG.md with the changes since the last release, bump and tag every plugin that changed as {plugin-name}--v{version} so a version-constrained dependency can resolve, and publish a GitHub release crediting every merged pull request and closed issue to the people behind it. Use when…
release-expert
Multi-repo release coordination: version alignment, RC lifecycle, release waves, rollback planning. Use when saying "release", "version alignment", or "cut an RC".
release
Guide through the Cortex TMS release process — version bump, changelog, sync, tag, publish. Every step requires user approval.
changelog
Record shipped work in the monthly changelog (append-only). Use when something ships or when asked "what changed", "add to changelog", "release notes", or "what shipped this month".
ship
Ship a build — pre-flight checks, deploy, document, verify, monitor. Use when deploying code, publishing packages, or releasing.
ship-item
Ship a plan/todo item in a documentation-led repo — run the verify gate, integrate per the repo's model (fast-forward or PR), git mv todo→done with a shipped footer, advance the owning ADR(s) to Implemented, and regenerate INDEX. Use when the user says "ship this", "complete the plan item", "mark done", or "close out…