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 bostonaholic/team --skill changeloggit clone --depth 1 https://github.com/bostonaholic/teamWrote 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/bostonaholic/team/changelog)<a href="https://agentmods.dev/skills/bostonaholic/team/changelog"><img src="https://agentmods.dev/badge/skills/bostonaholic/team/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/bostonaholic/team/changelog"><img src="https://agentmods.dev/badge/skills/bostonaholic/team/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.00026 | $0.00705 |
| Opus 5 | $0.00013 | $0.00352 |
| Sonnet 5 | $0.00005 | $0.00141 |
| Haiku 4.5 | $0.00003 | $0.00071 |
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 4d 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 — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Changelog
Maintain a curated user-facing CHANGELOG.md under Keep a Changelog. Every entry answers “How does this affect me?” Create the root file if missing.
Write at seventh-grade, STE-flavored level. Before finalizing, call the Skill tool with writing-prose and apply its ## Self-lint.
Structure
All changes stay under ## [Unreleased] until an explicit release. Each bullet belongs to exactly one of Added, Changed, Deprecated, Removed, Fixed, or Security; always document vulnerability fixes. On release only, rename it using [X.Y.Z] - YYYY-MM-DD as ## [X.Y.Z] - YYYY-MM-DD and add a new empty [Unreleased] above it. Read references/format-and-examples.md when creating the file or choosing a section.
Candidate selection
Before classifying commits, read references/baseline-and-filter.md and execute its baseline commands. Every commit after the most recent release is a candidate; if no versioned heading exists, use the root commit. Read ambiguous diffs; never classify from an unclear subject.
Include every feat:, fix:, perf:, BREAKING CHANGE:, and security: or security-related fix. Exclude internal-only chore:, test:, refactor:, docs:, ci:, revert:, WIP, fixup, and merge commits. A dependency or docs-only change earns an entry only when users experience the result; describe that result. If a feature and its revert occur in one release, include neither.
Ship-phase procedure
- Read
[Unreleased]; skip every change already covered. An unchanged second run writes nothing. - Find the baseline, list later commits, inspect ambiguous diffs, and apply the filter.
- Merge commits that implement one user-visible change into one bullet. Sort each section by user impact.
- Commit the changelog with the code it documents. If nothing survives, leave
CHANGELOG.mduntouched and report that result.
Rules
- Describe user-observable results, never implementation details. One user-visible change gets one short bullet of one or two sentences.
- Never duplicate an entry; reruns are idempotent.
- Write in past tense: “Added X,” not “Add X.”
- Use absolute URLs for links because released sections become GitHub release notes. Use
https://github.com/<owner>/<repo>/blob/<default-branch>/<path>or published docs; never repository-relative links. Bare#anchorsandmailto:are allowed. - Relative
[versioning](docs/versioning.md)links break in release notes; replace them with fullhttps://…URLs. - A changelog rebase conflict keeps both: branch entries remain under
[Unreleased], above the base’s newest## [X.Y.Z]; every dated base section remains unchanged. - Always update
[Unreleased]. Never create a versioned section unless the user explicitly requests a release.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago Changed · -190 lines · -3 tokens per session 2f61d8f29f9c
- 6d ago Changed · +6 lines 9770c45fb5c0
- 9d ago First seen · 223 lines · 29 tokens per session scan A e3d74fcae58d
changelog is a skill published in the GitHub repository bostonaholic/team (11 stars, last pushed today), licensed MIT. It adds 26 tokens to every session and 705 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-08-30.
Other skills, from other repositories
git-integration
Git commit patterns, formats, and conventions for GSD methodology. Provides atomic commits per task, structured commit messages, planning file commits, branch management, and milestone tag operations.
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work.
audit-trail
Full traceability from PRD to code commit through the CCPM spec-driven pipeline.
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
maintenance-orchestration
Technical debt management including branch cleanup, doc verification, TODO scanning, and dependency auditing.
worktree-isolation
Manage git worktree lifecycle for safe, isolated parallel development.