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/kaeawc/auto-mobile/push-prnpx skills add kaeawc/auto-mobile --skill push-prgit clone --depth 1 https://github.com/kaeawc/auto-mobileWrote 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/kaeawc/auto-mobile/push-pr)<a href="https://agentmods.dev/skills/kaeawc/auto-mobile/push-pr"><img src="https://agentmods.dev/badge/skills/kaeawc/auto-mobile/push-pr.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.00053 | $0.00752 |
| Opus 5 | $0.00026 | $0.00376 |
| Sonnet 5 | $0.00011 | $0.00150 |
| Haiku 4.5 | $0.00005 | $0.00075 |
Grade A, and why
push-pr 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Push PR
Use this when local work is ready to publish. This is the canonical publish workflow for this repo and replaces the old gh-pr-workflow helper plus any generic github:yeet defaults.
- Prefer
push-prfor one branch or one PR. - Prefer
push-my-prsonly when the user wants a batch loop across many PRs. - Use generic plugin publish skills only when this repo-local skill is unavailable.
Workflow
- Confirm scope before staging.
- Inspect
git status --short,git diff --stat, and recent commit style. - If the worktree contains unrelated or user-owned changes, stage only explicit paths that belong to the PR.
- Use
git add -Aonly when the whole worktree is confirmed in scope.
- Inspect
- Determine the branch strategy.
- Stay on the current branch when it is already a work branch.
- If publishing from
main,master, or the remote default branch, create a repo-appropriatework/...branch unless the user requested a different name.
- Run the relevant validation before pushing.
- Prefer repo scripts and documented validation commands.
- Do not skip validation unless the user explicitly accepts that risk.
- Commit intentionally with a repository-appropriate message.
- Keep the commit message terse and descriptive.
- Do not amend or rewrite unrelated commits unless the user explicitly asks.
- Push the current branch, setting upstream if needed.
- Create or update exactly one PR.
- Prefer
gh pr view --json number,urlto detect an existing PR for the current branch. - If no PR exists, create one with
gh pr create. - If a PR exists, update it with
gh pr editonly when the title/body/base needs to change. - Use the GitHub app for PR creation only when the surrounding tool environment already provides it and the repository, base, and head can be resolved unambiguously; otherwise use
gh.
- Prefer
- Preserve PR body formatting.
- Write multiline PR bodies to
scratch/pr-body.mdor another temporary body file. - Use
gh pr create --body-file scratch/pr-body.mdorgh pr edit --body-file scratch/pr-body.md. - Avoid
--body "..."for multiline Markdown because shell quoting can mangle newlines.
- Write multiline PR bodies to
- Set PR readiness and automerge deliberately.
- Default to a ready PR when the user asked to publish completed work.
- Use a draft PR when the user asks for draft status or the work is intentionally incomplete.
- Enable squash automerge only when that matches the branch's intended workflow and the PR is ready.
- Summarize branch, commit, PR URL, validation, and any remaining risk.
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 · 61 lines · 53 tokens per session scan A f16e8cb35766
push-pr is a skill published in the GitHub repository kaeawc/auto-mobile (45 stars, last pushed today), licensed Apache-2.0. It adds 53 tokens to every session and 752 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…