Borrowing it
Nothing to install: this file belongs to Terry-Mao/AICodingFlow. 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/Terry-Mao/AICodingFlow/main/.github/skills/product-change-report/SKILL.mdgit clone --depth 1 https://github.com/Terry-Mao/AICodingFlowWrote 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/skills/terry-mao/aicodingflow/product-change-report)<a href="https://agentmods.dev/skills/terry-mao/aicodingflow/product-change-report"><img src="https://agentmods.dev/badge/skills/terry-mao/aicodingflow/product-change-report.svg" alt="Measured on agentmods" 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.00046 | $0.01548 |
| Opus 5 | $0.00023 | $0.00774 |
| Sonnet 5 | $0.00009 | $0.00310 |
| Haiku 4.5 | $0.00005 | $0.00155 |
Grade A, and why
product-change-report 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Change Report
Review recent code, spec, issue, and pull-request changes and generate a time-series product update report. The report records what changed and what may need follow-up; it is not the source of truth for long-term product knowledge and must not silently rewrite authoritative product docs.
The primary output path is:
docs/updates/auto-update-YYYY-MM-DD.md
Use docs/product/, specs, issues, PR descriptions, and implementation diffs as context for accurate reporting, but do not directly modify long-term product docs or compiled wiki pages from this skill.
Workflow
1. Identify Reportable Changes
Determine which recent changes should appear in the update report:
- Find the default branch
- Get recent commits (default: last 24 hours, or accept user-specified timeframe)
- Examine relevant merged PRs, commit diffs, PR descriptions, linked issues, and checked-in specs
- Compare the implementation diff against available product and technical specs when they exist
Include report entries for:
- New features or capabilities
- API changes (new endpoints, parameters, return values)
- Breaking changes
- New configuration options
- New CLI commands or flags
- Changes to user-facing behavior
- Bug fixes with visible user or workflow impact
- Internal engineering changes that affect reliability, maintainability, delivery workflow, or future product risk
- Risks, incomplete follow-ups, rollout notes, or validation still needed
- Possible candidates for long-term product docs synchronization
Skip report entries for:
- Internal refactoring
- Test-only changes
- Minor bug fixes
- Typo corrections in code
- Performance optimizations without user impact
Be conservative: quality over quantity. When a change is not clearly reportable, omit it. When a change is reportable but its long-term documentation impact is unclear, include it under possible docs sync candidates instead of updating product docs directly.
2. Analyze Report Context
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 · 137 lines · 46 tokens per session scan A 5065775fd25d
product-change-report is a skill published in the GitHub repository Terry-Mao/AICodingFlow (165 stars, last pushed 9d ago), licensed MIT. It adds 46 tokens to every session and 1,548 once invoked, about $0.0002 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-30.
Other skills, from other repositories
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
codex-autoresearch
Run autonomous, measurable experiments in a Git repository: change one hypothesis, verify a numeric metric, keep improvements, and revert failures. Use when the user wants Codex to keep iterating toward a numeric target in the foreground or as a detached background run. Do not use for ordinary one-shot coding…
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".