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/dirtybits/agent-skills/fix-bugbot-pr-commentsnpx skills add dirtybits/agent-skills --skill fix-bugbot-pr-commentsgit clone --depth 1 https://github.com/dirtybits/agent-skillsWrote 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/dirtybits/agent-skills/fix-bugbot-pr-comments)<a href="https://agentmods.dev/skills/dirtybits/agent-skills/fix-bugbot-pr-comments"><img src="https://agentmods.dev/badge/skills/dirtybits/agent-skills/fix-bugbot-pr-comments.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.01348 |
| Opus 5 | $0.00026 | $0.00674 |
| Sonnet 5 | $0.00011 | $0.00270 |
| Haiku 4.5 | $0.00005 | $0.00135 |
Grade A, and why
fix-bugbot-pr-comments 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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fix Bugbot PR Comments
Use this workflow to make a PR merge-ready after Cursor Bugbot or other automated review comments appear.
Core Rules
- Use
ghfor all GitHub operations. - Fetch unresolved review threads first; filter out resolved threads before reading comment bodies.
- Read only each comment body plus the minimum path, line, and URL needed to act.
- Fix only clear, correct, in-scope feedback.
- Keep changes minimal and scoped to the PR.
- Do not modify CI workflows or config just to make checks pass.
- Do not include unrelated files or generated artifacts in commits.
- If a branch requires signed commits and this environment cannot produce a verified signature, stop and report the exact blocker instead of force-pushing or bypassing rules.
Resolve PR Context
Start from the current branch:
git status --short --branch
gh pr view --json number,url,title,headRefName,baseRefName,mergeStateStatus,reviewDecision,isDraft
gh pr checks --json name,bucket,state,workflow,link
If there are local changes, determine whether they are yours and relevant before touching them.
Fetch Unresolved Comments
Use GraphQL so resolved threads are filtered before reading bodies. If a PR may have more than 100 review threads or 50 reviews, paginate with pageInfo { hasNextPage endCursor } and repeat until complete; do not silently assume first:100 covers everything:
OWNER_REPO="$(gh repo view --json owner,name -q '.owner.login + "/" + .name')"
OWNER="${OWNER_REPO%/*}"
REPO="${OWNER_REPO#*/}"
PR="$(gh pr view --json number -q .number)"
gh api graphql \
-f owner="$OWNER" \
-f repo="$REPO" \
-F number="$PR" \
-f query='query($owner:String!, $repo:String!, $number:Int!) {
repository(owner:$owner, name:$repo) {
pullRequest(number:$number) {
reviewThreads(first:100) {
nodes {
isResolved
isOutdated
path
line
comments(first:10) {
nodes {
author { login }
body
url
}
}
}
}
reviews(first:50) {
nodes {
author { login }
state
body
url
}
}
}
}
}' \
--jq '.data.repository.pullRequest as $pr |
{
unresolvedThreads: [
$pr.reviewThreads.nodes[]
| select(.isResolved == false)
| {path,line,isOutdated,comments:[.comments.nodes[] | {author:.author.login, body, url}]}
],
reviews: [$pr.reviews.nodes[] | {author:.author.login, state, body, url}]
}'
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 188 lines · 53 tokens per session scan A b207e3ea516e
fix-bugbot-pr-comments is a skill published in the GitHub repository dirtybits/agent-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 53 tokens to every session and 1,348 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-31.
Other skills, from other repositories
codeflow-maintainer
OpenClaw-only maintainer PR workflow modes and skills. For OpenCoven/coven PR creation, redirect to skills/pr-agent, the Coven PR Readiness Agent.
openclaw-dev
OpenClaw Dev Agent — OpenClaw-only docs-aware development assistant. For OpenCoven/coven PR creation, redirect to skills/pr-agent, the Coven PR Readiness Agent.
git-flow-pr
Executes the full PR-driven development workflow: create an isolated feature branch from the current work, commit all staged changes, rebase cleanly onto the selected base branch (skipping any ancestor commits already merged), push the branch, and open a GitHub pull request linked to a related issue. Includes guidance…
new-gh-issue-orchestration
Orchestrates a GitHub-issue-driven delivery workflow from issue intake to PR creation using reviewer-first then worker execution. Invoked when the user provides a GitHub issue link/number and asks to start end-to-end delivery.
github-design
Use when setting up GitHub repositories, workflows, issue templates, or project organization - enforces best practices for .github folder structure, reusable workflows, branch protection, CODEOWNERS, labels, and GitHub Projects. Triggers on: GitHub, repository setup, workflow, Actions, issue template, PR template…
github
GitHub workflow — creating and managing repos, always working on feature/development branches (never committing core changes directly to main), PR conventions, branch protection, and gh CLI patterns.