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.
git clone --depth 1 https://github.com/noizu-labs-ml/NoizuPromptLingoWrote 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/commands/noizu-labs-ml/noizupromptlingo/npl-update-changelog-docs)<a href="https://agentmods.dev/commands/noizu-labs-ml/noizupromptlingo/npl-update-changelog-docs"><img src="https://agentmods.dev/badge/commands/noizu-labs-ml/noizupromptlingo/npl-update-changelog-docs/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/commands/noizu-labs-ml/noizupromptlingo/npl-update-changelog-docs"><img src="https://agentmods.dev/badge/commands/noizu-labs-ml/noizupromptlingo/npl-update-changelog-docs.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.00000 | $0.01057 |
| Opus 5 | $0.00000 | $0.00528 |
| Sonnet 5 | $0.00000 | $0.00211 |
| Haiku 4.5 | $0.00000 | $0.00106 |
Grade A, and why
npl-update-changelog-docs 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 7d 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.md — Maintenance Guide (Milestone-Based, Monorepo-Aware)
Purpose
CHANGELOG.md at the project/sub-project root (NOT under docs/) records what changed, grouped into milestones rather than versions — this monorepo doesn't version components independently, so meaningful clusters of change get named milestones anchored to git tags at their historical boundary commits.
Structure & Placement
<component-root>/
├── CHANGELOG.md # Newest first; milestone entries
└── docs/ ... # (changelog does NOT live here)
Entry Format
# Changelog — {component}
## [Unreleased]
- [Accumulating changes since the last milestone tag]
## [m4-provider-expansion] — 2026-06-12 — tag: `utilities-media-tool/m4-provider-expansion`
Milestone summary: one or two sentences on what this cluster achieved.
### Added
- groq_chat provider; 13 providers total across 3 categories
### Changed
- Quality-fallback loop now eval-gated via lmstudio-proxy
### Fixed
- ...
### Removed
- ...
Rules: newest first; omit empty subsections; every milestone entry carries its date and tag; published entries are append-only — never rewrite history, add a correction note instead.
Milestone & Tag Conventions
- Milestones, not semver: name clusters by what they accomplished —
m1-initial-tooling,m3-rust-rewrite— numbered in landing order - Tag naming:
<component-slug>/<milestone>where component-slug is the path with/→-(e.g.utilities/media-tool→utilities-media-tool/m4-provider-expansion); the slug prefix keeps monorepo tags collision-free - Tag placement: annotated tag on the last commit belonging to the milestone:
git tag -a <name> -m "<summary>" <commit> - Do not push tags without explicit user go-ahead — creating local tags is reversible; pushing publishes them
Back-Population Procedure (No Existing Changelog)
- Scope history to the component:
git log --oneline --follow -- <path>(subtree moves matter — check old paths too) - Read messages first; when a message is inadequate to know what actually changed, inspect the change itself:
git show --stat <sha>, then the diff for the files that matter - Cluster commits into milestones: look for natural boundaries — feature landings, rewrites, long gaps, "big cluster then quiet" rhythms; a milestone should be tellable as one story
- Name each cluster, write its entry (summary + Added/Changed/Fixed/Removed), date it by its final commit
- Tag each milestone boundary commit per the convention above
- Anything after the last milestone boundary goes to
[Unreleased]
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.
- 7d ago First seen · 89 lines · 0 tokens per session scan A a2dc2f68e7eb
npl-update-changelog-docs is a command published in the GitHub repository noizu-labs-ml/NoizuPromptLingo (13 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,057 tokens. 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-09-04.
Other commands, from other repositories
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
handoff
Export a Waybill Bundle by default, or import one when requested.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.