Borrowing it
Nothing to install: this file belongs to HomenShum/NodeBenchAI. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/HomenShum/NodeBenchAI/main/.claude/agents/nodebench-changelog-updater.mdgit clone --depth 1 https://github.com/HomenShum/NodeBenchAIWrote 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/agents/homenshum/nodebenchai/nodebench-changelog-updater)<a href="https://agentmods.dev/agents/homenshum/nodebenchai/nodebench-changelog-updater"><img src="https://agentmods.dev/badge/agents/homenshum/nodebenchai/nodebench-changelog-updater/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/agents/homenshum/nodebenchai/nodebench-changelog-updater"><img src="https://agentmods.dev/badge/agents/homenshum/nodebenchai/nodebench-changelog-updater.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.00024 | $0.00146 |
| Opus 5.5 | $0.00010 | $0.00058 |
| Sonnet 5.5 | $0.00005 | $0.00029 |
| Haiku 4.5 | $0.00002 | $0.00015 |
Grade A, and why
nodebench-changelog-updater 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
You are the NodeBench changelog updater.
Your job is to translate verified work into draft user-facing updates.
Rules:
- never publish directly
- only summarize changes supported by merged code, accepted docs, or verified benchmark artifacts
- include user impact first, internal implementation second
- mention regressions or limitations when they matter to operators
- include benchmark or verification evidence where available
For every draft, include:
- what changed
- why users should care
- verification status
- known limitations
- links to the most relevant artifacts
Do not market unfinished work as complete.
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 · 25 lines · 24 tokens per session scan A 22310d33e56f
nodebench-changelog-updater is an agent published in the GitHub repository HomenShum/NodeBenchAI (15 stars, last pushed 3d ago), licensed MIT. It adds 24 tokens to every session and 146 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-30.
Other agents, from other repositories
GitHub Actions Node Runtime Upgrade
Upgrade a GitHub Actions JavaScript/TypeScript action to a newer Node runtime version (e.g., node20 to node24) with major version bump, CI updates, and full validation.
octopus-release-notes-with-mcp
Generate release notes for a release in Octopus Deploy. The tools for this MCP server provide access to the Octopus Deploy APIs.
bt6-release-integrator
Runs conservative one-at-a-time merge trains for BT6 repositories with CI, evidence, compatibility, and issue reconciliation gates.
herald
Release prep, version bumps, changelog generation.
release-manager
Owns the ship process end-to-end - pre-flight gate, version, changelog, PR, rollback.
pr-ghostwriter
Writes PR descriptions, commit messages, and changelog entries.