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 kombohq/company-brain --skill update-changeloggit clone --depth 1 https://github.com/kombohq/company-brainWrote 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/kombohq/company-brain/update-changelog)<a href="https://agentmods.dev/skills/kombohq/company-brain/update-changelog"><img src="https://agentmods.dev/badge/skills/kombohq/company-brain/update-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/kombohq/company-brain/update-changelog"><img src="https://agentmods.dev/badge/skills/kombohq/company-brain/update-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.00051 | $0.00538 |
| Opus 5 | $0.00026 | $0.00269 |
| Sonnet 5 | $0.00010 | $0.00108 |
| Haiku 4.5 | $0.00005 | $0.00054 |
Grade A, and why
update-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 11d 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
Update the changelog
This repo keeps a human-scannable CHANGELOG.md at the repo root
(Keep a Changelog format). Every
user-facing change records a terse bullet under ## [Unreleased] so a release
can be cut at any time from accumulated entries.
When to add an entry
- Add one for: a new feature, a behavior change, a bug fix, a removed feature, or anything a user of this repo would notice.
- Skip: pure internal churn (refactors, formatting, test-only changes, dep bumps) unless it's notable enough that someone would want to know.
When in doubt, add a short bullet. A missing entry is worse than a small one.
How to add it
Edit CHANGELOG.md directly. Put the bullet under ## [Unreleased], in the
right group, creating the ### subheading if it isn't there yet:
### Added— new features### Changed— changes to existing behavior### Fixed— bug fixes### Removed— removed features
Style
- One terse bullet, imperative mood, matching the brevity of existing entries.
- No version number and no date — those are filled in at release time.
- Name the connector/area when it helps, e.g.
Slack connector: sync channel history.
Example
Before:
## [Unreleased]
## [1.0.0] - 2026-06-18
After adding a new connector:
## [Unreleased]
### Added
- Slack connector: sync channel history into `context/`
## [1.0.0] - 2026-06-18
Releasing
scripts/release.sh (run via bun run release) consumes everything under
## [Unreleased] at release time, rolling it into a dated version section and
opening a fresh empty [Unreleased]. Keeping [Unreleased] current as you work
is what makes the next release accurate, so add the bullet in the same change
that introduces the feature or fix.
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.
- 11d ago First seen · 70 lines · 51 tokens per session scan A fbcefb99ec9a
update-changelog is a skill published in the GitHub repository kombohq/company-brain (20 stars, last pushed 2mo ago), licensed MIT. It adds 51 tokens to every session and 538 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
commit-pr
Mandatory Codex/Copilot publication adapter for opencode-swarm. Use for every GitHub issue assignment that results in code changes, commits, pushes, draft PRs, PR body edits, PR readying, release notes, or CI closeout. Must be loaded before git push, gh pr create, gh pr edit, or gh pr ready. Routes to the single…
contributing
Codex adapter for the opencode-swarm contribution checklist. Use when preparing user-visible changes, release note fragments, local validation, branch hygiene, PR checklist items, or contribution-policy compliance before publishing work.
release-aur
Use when creating, updating, reviewing, or publishing Arch User Repository (AUR) packages. Runs /release-aur plan first, reviews PKGBUILD/.SRCINFO/build/namcap evidence, and only recommends /release-aur publish after a GO decision.
deploy-safely
Build, test, push, deploy, and verify with rollback through Git on failure.
fable-release
Audit and certify repository merge and release readiness against required quality gates, clean git working trees, and verified distribution artifacts. Use when preparing a release tag, validating release checklist criteria, publishing npm/PyPI packages, or certifying a branch for merge — even if the user does not…
release
Cut a release of the msteams channel plugin — validate, bump the version in all four manifests, write a CHANGELOG entry, commit, push, tag, and publish a GitHub release. Use whenever the user says "release", "cut a release", "version bump", "ship it", "publish", "tag a release", "changelog and push", or finishes a…