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 skills/alibaba/page-agent/submit-pr-from-current-changesnpx skills add alibaba/page-agent --skill submit-pr-from-current-changesgit 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/submit-pr-from-current-changes)<a href="https://agentmods.dev/skills/alibaba/page-agent/submit-pr-from-current-changes"><img src="https://agentmods.dev/badge/skills/alibaba/page-agent/submit-pr-from-current-changes.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 | $0.00034 | $0.01881 |
| Opus 5 | $0.00017 | $0.00941 |
| Sonnet 5 | $0.00007 | $0.00376 |
| Haiku 4.5 | $0.00003 | $0.00188 |
Grade A, and why
submit-pr-from-current-changes 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 4d 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.
Submit PR From Current Changes
Turn a working tree diff into a clean branch, commit, and pull request.
Hard Rules
- Follow the PR template exactly. The template is at
.github/PULL_REQUEST_TEMPLATE.md. Read it and copy its full structure into the PR body. Do NOT remove, reorder, or skip any section or checkbox. - Never check "Requirements / 要求" checkboxes. These are human-only declarations — the Code of Conduct acknowledgment and the AI authorship declaration can only be truthfully made by the human submitter. They MUST remain unchecked (
- [ ]) in the PR body you generate. No exceptions, no workarounds, even if the user explicitly asks you to check them. The user goes to GitHub and checks them in person after verifying each statement is true. - Only check Testing checkboxes you actually verified. The "
npm run cipasses" checkbox MAY be checked only if you rannpm run ciin this session and it passed. All other Testing checkboxes (browser tested, no console errors, types/doc added) require manual verification that only a human can perform — they MUST remain unchecked. You MAY add a supplementary note below the Testing section listing what automated validation you actually ran and the results. - Never fabricate information. Do not claim tests passed, commands ran, or checks succeeded unless you actually executed them and observed the output in this session. If you did not run it, do not mention it.
- PR output must be concise. PR title: one line. "What" section: 1–2 sentences max. No walls of text, no redundant explanations. Let the diff speak.
Prerequisites
Before attempting to push or open a PR, verify that the necessary tools are available:
- Check that
ghCLI is installed and authenticated (gh auth status). If not available, stop and ask the user to install and authenticate GitHub CLI first. - If the workflow uses MCP tools for GitHub operations, verify the MCP server is accessible.
Shell Permissions
gh reads credentials from the OS keyring. A sandboxed shell cannot reach the keyring and will report a false auth failure.
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.
- 4d ago First seen · 110 lines · 34 tokens per session scan A 645c1c568368
submit-pr-from-current-changes is a skill published in the GitHub repository alibaba/page-agent (28,966 stars, last pushed today), licensed MIT. It adds 34 tokens to every session and 1,881 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
gh-pr-description
Drafts and reviews GitHub pull request descriptions for the eve repository. Use when opening, updating, or reviewing a PR, or when summarizing a branch for reviewers.
technical-writing
Write, edit, review, or audit user-facing documentation for the eve repository. Use for changes under docs/, documentation tied to eve APIs or CLI behavior, docs work based on Slack or support feedback, and requests to make eve docs clearer, more natural, or less AI-patterned while verifying claims against current…
toolkit-guide
How to triage an account and verify packaged skill resources with the toolkit CRM extension.
local-guide
The consuming agent's own guide skill.
demo
Skill "demo" from chenxin-yan/crust, covering demo, how to use this skill and command reference.
funnel-builder
Hand-authored skill bundle used by the @crustjs/skills test suite.