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 commands/techgardencode/naive-user/update-changeloggit clone --depth 1 https://github.com/TechGardenCode/naive-userWhat 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.00018 | $0.00372 |
| Opus 5 | $0.00009 | $0.00186 |
| Sonnet 5 | $0.00004 | $0.00074 |
| Haiku 4.5 | $0.00002 | $0.00037 |
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 yesterday.
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
Keep CHANGELOG.md current. This is a maintainer tool for developing this repo, not part of
the shipped plugin.
- Run
git diff HEADandgit statusto see what changed since the last commit. If nothing is staged or modified, also look at commits since the latest tag (git log $(git describe --tags --abbrev=0 2>/dev/null)..HEAD --oneline). - Summarize the changes a user of the plugin would notice, not the mechanics. Sort each
entry under the right Keep a Changelog heading:
Added,Changed,Deprecated,Removed,Fixed,Security. - Edit
CHANGELOG.md: merge those entries into the## [Unreleased]section. Do not duplicate an entry that is already there. Keep the prose plain, no em dashes. - If
$ARGUMENTSnames a version, cut a release: rename## [Unreleased]to## [<version>] - <today's date in YYYY-MM-DD>, add a fresh empty## [Unreleased]above it, bump theversionfield in every plugin manifest (.claude-plugin/plugin.json,.codex-plugin/plugin.json,.github/plugin/plugin.json,gemini-extension.json), and update the compare links at the bottom of the changelog. - Show the diff you made. Do not commit unless asked.
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.
- yesterday First seen · 23 lines · 18 tokens per session scan A 451f27688585
update-changelog is a command published in the GitHub repository TechGardenCode/naive-user (1 stars, last pushed 1mo ago), licensed MIT. It adds 18 tokens to every session and 372 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-31.
Other commands, from other repositories
debug-react
Inspect a live React runtime with React-Sentinel before editing source code.
reproduce-bug
Reproduce a React or browser bug with React-Sentinel before proposing a fix.
validate-fix
Validate a proposed React fix with React-Sentinel assertions or replay checks.
specify
Create or update the feature specification from a natural language feature description.
speckit.git.validate
Validate current branch follows feature branch naming conventions.
read
Read a specific section from an arXiv paper's HTML version (ar5iv.org).