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/baseballyama/eslint-plugin-postgresql/review-responsenpx skills add baseballyama/eslint-plugin-postgresql --skill review-responsegit clone --depth 1 https://github.com/baseballyama/eslint-plugin-postgresqlWrote 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/baseballyama/eslint-plugin-postgresql/review-response)<a href="https://agentmods.dev/skills/baseballyama/eslint-plugin-postgresql/review-response"><img src="https://agentmods.dev/badge/skills/baseballyama/eslint-plugin-postgresql/review-response.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.00075 | $0.01820 |
| Opus 5 | $0.00037 | $0.00910 |
| Sonnet 5 | $0.00015 | $0.00364 |
| Haiku 4.5 | $0.00007 | $0.00182 |
Grade A, and why
review-response 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 — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Responding to review comments
GitHub review comments are a back-and-forth, not a checklist. The right loop: fetch unresolved → decide per comment with the user → fix or decline → reply → repeat.
Principles
| Principle | Detail |
|---|---|
| Only unresolved threads | If the reviewer marked it resolved, don't reopen it. |
| One at a time | Even with many comments, address them sequentially. |
| Always reply | Every comment gets a response — fix or explain. |
| Reference the commit hash | Replies that say "fixed" without a hash leave the reviewer guessing. |
| Decline with a reason | "Won't fix" is fine; silent or hand-wavy "won't fix" is not. |
| Get user approval first | Decide the plan with the user before posting anything visible. |
Step 0 — Fetch unresolved threads
GitHub's REST endpoint returns all review comments — including resolved ones. Use GraphQL to filter for unresolved.
# All unresolved review threads on a PR
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
isOutdated
comments(first: 20) {
nodes {
id
databaseId
author { login }
body
path
line
url
}
}
}
}
}
}
}
' -f owner=<owner> -f repo=<repo> -F pr=<pr>
Filter the result client-side for isResolved == false. Each thread's first comment
is the original; the rest are replies. You're addressing the original, but read the
whole thread — the reviewer may have already self-answered, or another contributor
may have responded.
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 · 204 lines · 75 tokens per session scan A 307aa494ba72
review-response is a skill published in the GitHub repository baseballyama/eslint-plugin-postgresql (11 stars, last pushed yesterday), licensed MIT. It adds 75 tokens to every session and 1,820 once invoked, about $0.0004 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…