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/pr-analysisnpx skills add kaeawc/auto-mobile --skill pr-analysisgit 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/pr-analysis)<a href="https://agentmods.dev/skills/kaeawc/auto-mobile/pr-analysis"><img src="https://agentmods.dev/badge/skills/kaeawc/auto-mobile/pr-analysis.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.00046 | $0.00395 |
| Opus 5 | $0.00023 | $0.00198 |
| Sonnet 5 | $0.00009 | $0.00079 |
| Haiku 4.5 | $0.00005 | $0.00040 |
Grade A, and why
pr-analysis 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.
What it actually says
PR Analysis
Perform a read-only PR review that covers intent, correctness, regression risk, tests, and existing feedback.
Workflow
- Resolve the PR with
gh pr view <pr> --json ...and capture the head branch, base branch, title, and body. - Gather context with
gh pr diff,gh pr diff --stat,gh pr checks, and all paginated review, inline, and conversation comments plus review verdicts. - Always collect GraphQL review-thread state: unresolved and outdated threads are not
represented reliably by flat comment views. Reuse
github-pr-feedbackfor the collection and the ledger. - Read full changed files from the PR branch and the base branch, not just diff hunks.
- Find related callers, interfaces, and tests in the local codebase.
- If validation is warranted, run the lightest relevant repo validation rather than a blanket heavy build.
- Produce findings first, then open questions, then a short summary.
Repo Rules
- Prefer
ghfor PR metadata and CI data. - Prefer repo validations:
- TypeScript:
bun run lint,bun run build,bun test - Fast checks:
bash scripts/all_fast_validate_checks.sh - Android or iOS only when the PR actually touches those areas
- TypeScript:
- Keep the analysis read-only unless the user explicitly asks for fixes.
- When saving large diffs or logs, put them in
scratch/.
Output Structure
- Findings ordered by severity with
file:linereferences - Open questions or assumptions
- Brief change summary and residual risks
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 · 38 lines · 46 tokens per session scan A b360ad0584ec
pr-analysis is a skill published in the GitHub repository kaeawc/auto-mobile (45 stars, last pushed today), licensed Apache-2.0. It adds 46 tokens to every session and 395 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
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…