Page Agent is a JavaScript library that embeds a natural-language agent inside a web page and lets it operate the page through its text-based DOM. It is used for web copilots, form filling, accessibility, and browser workflows, while the catalogue entries provide agent skills and instructions for using it.
Borrowing it
Nothing to install: this file belongs to alibaba/page-agent. 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/alibaba/page-agent/main/.agents/skills/update-changelog/SKILL.mdgit clone --depth 1 https://github.com/alibaba/page-agentWrote 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/alibaba/page-agent/update-changelog)<a href="https://agentmods.dev/skills/alibaba/page-agent/update-changelog"><img src="https://agentmods.dev/badge/skills/alibaba/page-agent/update-changelog/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/skills/alibaba/page-agent/update-changelog"><img src="https://agentmods.dev/badge/skills/alibaba/page-agent/update-changelog.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Snyk pass
- NVIDIA SkillSpector pass
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.00052 | $0.00777 |
| Opus 5 | $0.00026 | $0.00388 |
| Sonnet 5 | $0.00010 | $0.00155 |
| Haiku 4.5 | $0.00005 | $0.00078 |
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 10d 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Changelog
Update docs/CHANGELOG.md from repository evidence instead of guesswork.
When to Use
- Add the newest release entry to
docs/CHANGELOG.md - Sync changelog text with GitHub Releases
- Summarize the latest tag from git history or code diffs
Defaults
- Keep the wording brief
- Only add the latest missing version unless the user explicitly asks to backfill older releases
- Prefer GitHub sources first, especially Releases and tag metadata
- Skip
Features/Improvements/Bug Fixesheadings when the release only has a few clear items
Procedure
1. Read the local style
- Open
docs/CHANGELOG.md - Match the existing tone, bullet style, section ordering, and date format
2. Determine the target release
- Read the root
package.jsonversion and compare it with the top changelog entry - Find the previous tag for the target version
- If the latest version is already documented, stop and report that no changelog update is needed
3. Gather evidence
Prefer these sources in order:
- GitHub release notes
GH_PAGER=cat gh release view v<version> --repo <owner>/<repo> --json tagName,name,publishedAt,body
- Tag date
git log -1 --format=%cs v<version>
- Commit history between tags
git --no-pager log --format='%h %s' --no-merges v<previous>..v<version>
- Diff scope when commit subjects are vague
git --no-pager diff --name-only v<previous>..v<version>
git --no-pager diff --stat v<previous>..v<version>
- Read touched files directly only when the user-visible change is still unclear
4. Distill what belongs in the changelog
Include:
- User-visible features
- Important behavior changes
- Bug fixes that improve reliability, compatibility, or developer experience
- Small docs updates only when they materially change supported setups or onboarding
Exclude unless explicitly requested:
- Pure version bumps
- Routine dependency updates
- Internal refactors with no visible impact
- Mechanical formatting noise
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.
- 10d ago First seen · 110 lines · 52 tokens per session scan A 6d77a574f02d
update-changelog is a skill published in the GitHub repository alibaba/page-agent (29,017 stars, last pushed yesterday), licensed MIT. It adds 52 tokens to every session and 777 once invoked, about $0.0003 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
publish-npm-packages
Configure, audit, or migrate npm package publishing to current secure practices. Use when Codex needs to publish or prepare an npm package, fill npm Trusted Publisher settings, create a GitHub Actions/GitLab/CircleCI release workflow, adopt OIDC, replace npm tokens, publish organization-scoped public or private…
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. Use when the user wants to create a pull request, open a PR, or submit changes for review.
draft-release-notes
Author the committed release-notes file for a Prisma 8 release (stable or 8.0.0-rc.N) by enumerating the merged PRs since the previous release v tag (stable or -rc.N), resolving opaque TML-NNNN: titles via Linear context (never copied verbatim), triaging public-worthiness, and writing categorized notes — breaking…
contrib-pr
Open a high-quality external contributor PR against prisma/orm. Use when the user is an outside contributor (not a Prisma maintainer) and wants to submit a change as a pull request from a fork. Encodes the contribution flow from CONTRIBUTING.md so the resulting PR passes review on the first round.
triage-contributor-pr
Triage open pull requests from external contributors to prisma/prisma and produce a per-PR verdict with evidence. Use when a maintainer asks to triage, evaluate, assess, or review the queue of incoming contributor PRs, to decide whether a fork PR is safe to run CI on, to check whether a PR is in scope for its version…
publish-npm-version
Cuts the next release of Prisma 8: bumps the root package.json version (on the v8 RC line: 8.0.0-rc.N → rc.N+1), propagates it to every workspace package, and opens a PR titled "chore(release): bump to ". When the maintainer merges the PR, the Publish to npm workflow runs automatically and ships the new version to npm…