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/p2ergmbh/agentic-coding/review-pull-requestnpx skills add P2ERGmbH/agentic-coding --skill review-pull-requestgit clone --depth 1 https://github.com/P2ERGmbH/agentic-codingWhat 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.00041 | $0.01951 |
| Opus 5 | $0.00020 | $0.00975 |
| Sonnet 5 | $0.00008 | $0.00390 |
| Haiku 4.5 | $0.00004 | $0.00195 |
Grade A, and why
review-pull-request 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 2d 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Pull Request Review Workflow
This workflow guides you through an extensive and in-depth review of a GitHub Pull Request using the GitHub MCP integration. You act as an uncompromising senior architect and CI/CD gatekeeper.
Trigger
Use this workflow when requested to "review pull request #X", "run a PR review", or when executing within a GitHub Actions review workflow.
Phase 1: Isolated Git Worktree Setup (MANDATORY)
To ensure the review is conducted on the actual PR codebase with full lint, compile, and verification capabilities without polluting your main workspace, you MUST first set up an isolated Git Worktree:
- Identify the PR Branch: Fetch the PR branch name (
$PR_BRANCHor$HEAD_BRANCH) usingmcp_github_get_pull_request. - Create or Switch to Dedicated Worktree:
The dedicated worktree directory is
worktrees/pr-<PR_NUMBER>.- If the worktree directory DOES NOT exist:
Create it by cloning/adding the PR branch into the dedicated worktree directory:
Note: If the branch isn't available locally, fetch it from origin first:git worktree add worktrees/pr-<PR_NUMBER> <PR_BRANCH>git fetch origin pull/<PR_NUMBER>/head:<PR_BRANCH> git worktree add worktrees/pr-<PR_NUMBER> <PR_BRANCH> - If the worktree directory ALREADY exists:
Switch to the directory and pull the latest changes:
cd worktrees/pr-<PR_NUMBER> && git pull
- If the worktree directory DOES NOT exist:
Create it by cloning/adding the PR branch into the dedicated worktree directory:
- Copy Environment Configuration:
Copy the
.envfile from the root project directory into the worktree directory:cp .env worktrees/pr-<PR_NUMBER>/.env - Symlink Node Modules:
Symlink the
node_modulesdirectory from the root project directory to the worktree directory to avoid duplicate installation overhead:ln -s ../../node_modules worktrees/pr-<PR_NUMBER>/node_modules - Start the Review:
Execute all subsequent context-gathering (reading files, checking imports) and local linting/compiling inside the dedicated worktree directory
worktrees/pr-<PR_NUMBER>.
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.
- 2d ago First seen · 120 lines · 41 tokens per session scan A e1da9c6778ac
review-pull-request is a skill published in the GitHub repository P2ERGmbH/agentic-coding (9 stars, last pushed 2mo ago), licensed MIT. It adds 41 tokens to every session and 1,951 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-31.
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…