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 nirelbaz/promptpit --skill changeloggit clone --depth 1 https://github.com/nirelbaz/promptpitWrote 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/nirelbaz/promptpit/changelog)<a href="https://agentmods.dev/skills/nirelbaz/promptpit/changelog"><img src="https://agentmods.dev/badge/skills/nirelbaz/promptpit/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/nirelbaz/promptpit/changelog"><img src="https://agentmods.dev/badge/skills/nirelbaz/promptpit/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.00037 | $0.00317 |
| Opus 5.5 | $0.00015 | $0.00127 |
| Sonnet 5.5 | $0.00007 | $0.00063 |
| Haiku 4.5 | $0.00004 | $0.00032 |
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 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.
What it actually says
Changelog
Update CHANGELOG.md with recent changes.
Process
- Read the existing CHANGELOG.md (create one if it doesn't exist)
- Run
git log --onelinesince the last changelog entry to see what changed - Group changes by type and write the new entry
Format
Follow Keep a Changelog:
## [version] - YYYY-MM-DD
### Added
- New features
### Changed
- Changes to existing features
### Fixed
- Bug fixes
### Removed
- Removed features
Rules
- Write for users, not developers. "Fixed crash when saving empty form" not "Fixed null pointer in FormHandler.save()"
- Skip internal changes (refactors, test updates, CI tweaks) unless they affect users
- Group related changes into one bullet. "Redesigned settings page" not five separate bullets about each settings panel.
- Most recent version goes at the top
- If there's no CHANGELOG.md, create one with an Unreleased section at the top
- Link version headers to the git diff when possible:
[1.2.0]: https://github.com/user/repo/compare/v1.1.0...v1.2.0
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 · 45 lines · 37 tokens per session scan A 5e3a36618b07
changelog is a skill published in the GitHub repository nirelbaz/promptpit (6 stars, last pushed 2mo ago), licensed MIT. It adds 37 tokens to every session and 317 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-08-31.
Other skills, from other repositories
changelog-generator
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
share-a-library
Use when a managed library is ready to publish to GitHub and hand to teammates as an install command. Run the GitHub publishing steps, then return the exact shareable install command.
pypi-release
This skill should be used when releasing tunacode-cli to PyPI. It keeps the existing local release checks, then hands the actual PyPI upload to a GitHub Actions workflow that uses the repository's PYPIAPITOKEN secret.
changeset
USE WHEN: a change under apps/ or packages/ (or an app runtime dependency bump) needs its release note, the user asks to add, fix, or check a changeset, a PR is about to open, or pnpm release:check fails. DO NOT USE WHEN: editing the release pipeline itself (.changeset/config.json, release.yml, the check scripts) …
prepare-release
Use this skill whenever preparing agentsmesh for an npm release — whether first publish, patch, minor, or major. Triggers on: 'prepare release', 'ready to publish', 'ship version', 'release prep', 'get this to npm', 'bump version', 'cut a release', 'what's needed to publish'. Runs a strict ordered checklist: test…
release-manager
Tier: POWERFUL Category: Engineering Domain: Software Release Management & DevOps.