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/wrannaman/agentic-engineering/github-reviewnpx skills add wrannaman/agentic-engineering --skill github-reviewgit clone --depth 1 https://github.com/wrannaman/agentic-engineeringWhat 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.00020 | $0.02704 |
| Opus 5 | $0.00010 | $0.01352 |
| Sonnet 5 | $0.00004 | $0.00541 |
| Haiku 4.5 | $0.00002 | $0.00270 |
Grade A, and why
github-review 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 — 392 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Review Skill
You are entering the github-review phase. You will address review comments from a GitHub Pull Request.
Process
Step 0: Detect Stack Structure
Detect the active stack workflow using the git-stacks KB partition as the shared source of truth:
-
list_kb_documentsfor partitiongit-stacks -
read_kb_document_by_pathfor/index.md -
Run the dedicated-client checks from
git-stacks/index.md- If a dedicated client is detected, record
STACK_CLIENTaccordingly - If no dedicated client is detected, inspect the current PR base and local branch relationships to decide whether this repo is using a native git stack
- If confirmed, record
STACK_CLIENT=native-git
- If a dedicated client is detected, record
-
Load the matching KB client doc before running any stack-specific command:
charcoal→read_kb_document_by_pathfor/charcoal.mdgit-town→read_kb_document_by_pathfor/git-town.mdnative-git→read_kb_document_by_pathfor/native-git.md- Use the client doc as the source of truth for stack navigation commands
If in a stack:
- You may have multiple PRs with review comments
- Present option to address comments from all PRs or just current
Present to user (if in stack):
## Stack Detected
Your stack has N PRs with open review comments:
| PR | Branch | Open Comments |
|----|--------|---------------|
| #123 | feat/part-1 | 2 |
| #124 | feat/part-2 | 5 |
| #125 | feat/part-3 | 0 |
How would you like to proceed?
1. Address all PRs (recommended) - Fix comments across all PRs
2. Address current PR only (#124) - Fix comments on feat/part-2 only
Step 1: Pull OPEN (Unresolved) PR Review Comments
For stacked PRs: Pull comments from each PR in scope.
First, identify the PR(s) and pull only unresolved review threads using GraphQL (the REST API does not expose resolved/unresolved status):
# Get PR number and basic info from current branch
gh pr view --json number,title,url,reviewDecision
# Get ONLY unresolved review threads using GraphQL
gh api graphql -f query='
query($owner: String!, $repo: String!, $pr: Int!) {
repository(owner: $owner, name: $repo) {
pullRequest(number: $pr) {
reviewThreads(first: 100) {
nodes {
isResolved
path
line
comments(first: 10) {
nodes {
author { login }
body
createdAt
}
}
}
}
}
}
}' -f owner='{owner}' -f repo='{repo}' -F 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 · 392 lines · 20 tokens per session scan A a6e3549e522a
github-review is a skill published in the GitHub repository wrannaman/agentic-engineering (2 stars, last pushed 4mo ago), licensed MIT. It adds 20 tokens to every session and 2,704 once invoked, about $0.0001 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…