Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/andkirby/markdown-ticketnpx agentmods add commands/andkirby/markdown-ticket/update-notesWrote 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/andkirby/markdown-ticket/update-notes)<a href="https://agentmods.dev/commands/andkirby/markdown-ticket/update-notes"><img src="https://agentmods.dev/badge/commands/andkirby/markdown-ticket/update-notes/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/andkirby/markdown-ticket/update-notes"><img src="https://agentmods.dev/badge/commands/andkirby/markdown-ticket/update-notes.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.01399 |
| Opus 5.5 | $0.00000 | $0.00560 |
| Sonnet 5.5 | $0.00000 | $0.00280 |
| Haiku 4.5 | $0.00000 | $0.00140 |
Grade A, and why
update-notes 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.
How it starts
The opening of the file, as written. The whole thing — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Notes and Commit Changes
This command helps you update CHANGE_NOTES.md with changes made to mdt-*.md files and commit them with proper messages.
Options
--dry-run: Show what would be done without making changes--no-commit: Update files but don't commit--skip-version: Skip version increment step
Process
1. Analyze current changes
!git diff --name-only *.md
2. Read current CHANGE_NOTES.md
!cat CHANGE_NOTES.md
3. Analyze what changed
!git diff .
3.5. Check for renamed/moved files
IMPORTANT: When files are renamed or moved, git diff does not show changes by default. Use the -M flag to detect renames and show diffs properly:
# Show diff for a specific renamed file (before and after paths)
git diff --cached -M --unified=1 -- old/path.md new/path.md
# Show all renames with statistics
git diff --cached -M --stat
# Show rename detection for unstaged changes
git diff -M --unified=1 -- old/path.md new/path.md
This is critical when analyzing changes to reorganized workflows (e.g., commands/mdt-tasks.md → mdt/commands/tasks.md). Without -M, git treats these as delete+create pairs and you lose the diff context.
4. Determine if this is a new workflow or an update
Check if any mdt-*.md files are new or modified:
# List new mdt-*.md files
git status --porcelain *.md | grep "^??" | grep "mdt-.*\.md"
# List modified mdt-*.md files
git status --porcelain *.md | grep "^ M" | grep "mdt-.*\.md"
5. Version Increment FIRST (unless --skip-version)
IMPORTANT: Ask for version increment BEFORE writing CHANGE_NOTES.md so the entry contains the correct final version.
Read current plugin version:
!cat mdt/.claude-plugin/plugin.json | jq '.version'
Analyze changes and recommend version increment type:
Based on the changes detected, recommend the appropriate version increment:
| Change Type | Recommendation | Example |
|---|---|---|
| New command/workflow added | beta or minor |
0.10.0 → 0.11.0-beta |
| Breaking changes to existing workflow | beta or minor |
0.10.0 → 0.11.0-beta |
| Bug fixes, small improvements | patch |
0.10.0 → 0.10.1 |
| Beta iteration | beta |
0.11.0-beta → 0.11.0-beta.1 |
| Release stable from pre-release | release |
0.11.0-beta.22 → 0.11.0 |
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 · 168 lines · 0 tokens per session scan A 1ceea854fe8a
update-notes is a command published in the GitHub repository andkirby/markdown-ticket (7 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,399 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-08-31.
Other commands, from other repositories
commit-push-pr
Commit, push, and open a PR.
changelog-update
Actualiza CHANGELOG.md automáticamente analizando los commits desde la última versión/release. Clasifica los cambios por tipo (feat, fix, docs, etc.) usando los commits convencionales del workspace. Opcionalmente sugiere bump de versión semántica. Delega la redacción final a tech-writer.
changelog
Gera changelogs a partir do histórico git e valida commits convencionais. Uso: /changelog [opções].
commit
Smart conventional commit with security validation, branch flow enforcement, and auto-detection. Use for git commit, commit changes, save work, stage and commit.
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.
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.