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/gonzalezpazmonica/pm-workspaceWrote 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/gonzalezpazmonica/pm-workspace/changelog-update)<a href="https://agentmods.dev/commands/gonzalezpazmonica/pm-workspace/changelog-update"><img src="https://agentmods.dev/badge/commands/gonzalezpazmonica/pm-workspace/changelog-update/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/gonzalezpazmonica/pm-workspace/changelog-update"><img src="https://agentmods.dev/badge/commands/gonzalezpazmonica/pm-workspace/changelog-update.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.00068 | $0.00722 |
| Opus 5 | $0.00034 | $0.00361 |
| Sonnet 5 | $0.00014 | $0.00144 |
| Haiku 4.5 | $0.00007 | $0.00072 |
Grade A, and why
changelog-update 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 8d 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.
This is a copy
100% identical to changelog-update — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Actualización de CHANGELOG
Analiza los commits desde la última versión y actualiza
CHANGELOG.mdsiguiendo el formato "Keep a Changelog" (https://keepachangelog.com).
Protocolo
1. Identificar la última versión
# Buscar el último tag de versión
git tag --sort=-v:refname | head -5
# Si no hay tags, buscar la última entrada en CHANGELOG.md
head -30 CHANGELOG.md
2. Obtener commits desde la última versión
# Si hay tag
git log v{LAST_VERSION}..HEAD --oneline --no-merges
# Si no hay tag, desde el último cambio del CHANGELOG
git log --oneline --no-merges -50
3. Clasificar commits por tipo
Usando los tipos definidos en docs/rules/domain/github-flow.md:
| Tipo | Sección CHANGELOG |
|---|---|
feat |
### Added |
fix |
### Fixed |
docs |
### Documentation |
refactor |
### Changed |
chore |
### Maintenance |
test |
### Testing |
ci |
### CI/CD |
Ignorar commits de merge y commits del tipo wip.
4. Generar la nueva sección
Formato de cada entrada:
## [X.Y.Z] - YYYY-MM-DD
### Added
- Descripción clara del cambio (#PR o commit hash)
### Fixed
- Descripción del bug corregido
### Changed
- Descripción del cambio de comportamiento
5. Sugerir versión semántica
Analizar los commits para proponer el bump:
- MAJOR (X.0.0): si hay commits con
feat!:oBREAKING CHANGE - MINOR (0.X.0): si hay commits
feat:sin breaking changes - PATCH (0.0.X): si solo hay
fix:,docs:,chore:
Proponer al humano — NUNCA hacer bump automáticamente.
6. Delegar redacción final
Si el agente tech-writer está disponible, delegar la redacción final para
garantizar consistencia de tono y estilo con el resto del CHANGELOG.
7. Presentar al humano
Mostrar la sección generada y preguntar:
- ¿Versión propuesta es correcta?
- ¿Alguna entrada necesita ajuste?
- ¿Procedo a actualizar CHANGELOG.md?
Solo tras confirmación, escribir en el fichero.
Restricciones
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.
- 8d ago First seen · 104 lines · 68 tokens per session scan A cc45eb40d637
changelog-update is a command published in the GitHub repository gonzalezpazmonica/pm-workspace (49 stars, last pushed 6d ago), licensed MIT. It adds 68 tokens to every session and 722 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to changelog-update, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
commit-push-pr
Commit, push, and open a PR.
commit
Automatically generate commit message based on changes and push to current branch. Analyzes git diff to create meaningful commit following conventional commits format. Optionally creates and pushes a git tag.
commit
Smart conventional commit with security validation, branch flow enforcement, and auto-detection. Use for git commit, commit changes, save work, stage and commit.
changelog-auto
Auto-generar entradas de CHANGELOG.md desde commits convencionales. Usa cuando el usuario dice "generar changelog", "update changelog", "changelog", "conventional commits", "auto changelog", "release notes", "generar release notes", "伽 changelog". Genera entradas desde conventional commits (feat, fix, docs, etc.) con…
flow
Universal workflow entry point. Use /flow for skill-driven GitHub development. Verbs: start, commit, pr, review, address, merge, resolve, release, status, learn, setup, explain, debug, design, brainstorm, issue.
changelog
Gera changelogs a partir do histórico git e valida commits convencionais. Uso: /changelog [opções].