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/entireio/cli/changelognpx skills add entireio/cli --skill changeloggit clone --depth 1 https://github.com/entireio/cliWhat 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.00058 | $0.00837 |
| Opus 5 | $0.00029 | $0.00418 |
| Sonnet 5 | $0.00012 | $0.00167 |
| Haiku 4.5 | $0.00006 | $0.00084 |
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 3d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Changelog Generation
Generate a changelog entry for a new release by analyzing merged PRs since the last tag.
Parameters
The user provides:
- Version number -- e.g.,
0.5.3 - Additional PRs -- optionally, PRs not yet merged that should be included
Step 1: Gather Data
- Find the previous release tag:
git tag --sort=-version:refname | head -1 - List all merge commits since that tag:
git log <tag>..HEAD --merges --format='%s' | grep -v "Merge branch" - Get PR details with:
gh pr list --state merged --base main --search "merged:><tag-date>" --json number,title,author --limit 50 - List contributors:
git log <tag>..HEAD --format='%an' --no-merges | sort | uniq -c | sort -rn
Step 2: Identify External Contributors
To determine if a contributor is external, check for an @entire.io email:
git log --all --format='%an <%ae>' --author="<name>" | sort -u
If they have an @entire.io email anywhere in git history, they are internal. Only list external contributors in the Thanks section.
Also check the memory file at memory/project_team_members.md for known internal/external mappings.
Step 3: Write the Entry
Insert the new version section at the top of CHANGELOG.md, after the header and before the previous version.
Format
Follow the existing style in CHANGELOG.md exactly:
## [X.Y.Z] - YYYY-MM-DD
### Added
- Feature description with context ([#123](https://github.com/entireio/cli/pull/123))
### Changed
- Change description ([#456](https://github.com/entireio/cli/pull/456))
### Fixed
- Bug fix description ([#789](https://github.com/entireio/cli/pull/789))
### Housekeeping
- Maintenance item ([#101](https://github.com/entireio/cli/pull/101))
### Thanks
Thanks to @contributor for description of contribution!
Style Rules
- Sections: Added, Changed, Fixed, Housekeeping, Thanks. Omit empty sections.
- Each bullet: starts with a dash, concise description, PR link(s) at the end
- Group related PRs into a single bullet when they're part of the same feature/fix
- Work-in-progress features: call out explicitly, e.g., "Feature X (work in progress): ..."
- Known limitations: note inline, e.g., "Note: subagent tracking is not yet supported due to..."
- Thanks section: only external contributors. Name what they contributed specifically.
- Dependency bumps: group into a single Housekeeping bullet unless a bump fixes a notable bug
- PR links: always use full URL format
[#N](https://github.com/entireio/cli/pull/N) - No trailing period on bullet items
- Date: use the current date in YYYY-MM-DD format
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.
- 3d ago First seen · 89 lines · 58 tokens per session scan A 9cb353cbbdd3
changelog is a skill published in the GitHub repository entireio/cli (5,045 stars, last pushed yesterday), licensed MIT. It adds 58 tokens to every session and 837 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-30.
Other skills, from other repositories
merge_and_update
Merge the current PR, wait for merge queue/checks to complete, then switch to main and pull.
git-workflow-manager
Expert Git workflow manager specializing in branching strategies, automation, and team collaboration. Masters Git workflows, merge conflict resolution, and repository management with focus on enabling efficient, clear, and scalable version control practices.
agent-release-manager
Agent skill for release-manager - invoke with $agent-release-manager.
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
agent-github-modes
Agent skill for github-modes - invoke with $agent-github-modes.
agent-framework-py-release
Use when cutting a Python release for the microsoft/agent-framework monorepo. Triggers on "bump py versions", "cut a python release", "prepare release PR for python", "release py packages", "bump python to X.Y.Z", or similar requests to bump Python package versions and prepare a release PR. Handles all four lifecycle…