Borrowing it
Nothing to install: this file belongs to deslicer/mcp-for-splunk. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/deslicer/mcp-for-splunk/main/.cursor/commands/check-pr-feedback.mdgit clone --depth 1 https://github.com/deslicer/mcp-for-splunkWrote 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/commands/deslicer/mcp-for-splunk/check-pr-feedback)<a href="https://agentmods.dev/commands/deslicer/mcp-for-splunk/check-pr-feedback"><img src="https://agentmods.dev/badge/commands/deslicer/mcp-for-splunk/check-pr-feedback.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.1 | $0.00013 | $0.00695 |
| Opus 5 | $0.00006 | $0.00347 |
| Sonnet 5 | $0.00003 | $0.00139 |
| Haiku 4.5 | $0.00001 | $0.00069 |
Grade A, and why
check-pr-feedback 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 6d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Check PR Feedback and Fix Issues
You are tasked with checking for code review comments and CI workflow failures on a Pull Request, then resolving any issues found.
Steps to Follow
1. Get PR Information
First, identify the current PR number and repository. Use the GitHub CLI or API:
# Get current branch
git branch --show-current
# List open PRs for this branch
gh pr list --head $(git branch --show-current) --json number,title,url
2. Check for PR Review Comments
Fetch any code review comments added since PR creation:
# Get PR comments (replace PR_NUMBER)
gh api repos/OWNER/REPO/pulls/PR_NUMBER/comments --jq '.[] | {user: .user.login, body: .body, path: .path, line: .line}'
# Get PR review comments
gh api repos/OWNER/REPO/pulls/PR_NUMBER/reviews --jq '.[] | {user: .user.login, state: .state, body: .body}'
3. Check Workflow Status
Check all workflow runs for the latest commit:
# Get latest commit SHA
LATEST_SHA=$(gh api repos/OWNER/REPO/pulls/PR_NUMBER/commits --jq '.[-1].sha')
# Check workflow runs
gh api "repos/OWNER/REPO/actions/runs?head_sha=$LATEST_SHA" --jq '.workflow_runs[] | {name: .name, status: .status, conclusion: .conclusion, id: .id}'
4. Get Failed Job Details
For any failed workflows, get the specific job and step that failed:
# Get jobs for a failed run (replace RUN_ID)
gh api repos/OWNER/REPO/actions/runs/RUN_ID/jobs --jq '.jobs[] | select(.conclusion == "failure") | {name: .name, steps: [.steps[] | select(.conclusion == "failure") | .name]}'
5. Fix Issues
Based on the feedback:
- Code review comments: Address each comment by making the suggested changes
- Workflow failures:
- Run tests locally first:
uv run pytest -v - Run linting:
uv run ruff check src/ tests/ - Run type checking:
uv run mypy src/ - Fix any issues found
- Run tests locally first:
6. Commit and Push
After fixing issues:
git add -A
git commit -m "fix: address PR feedback
- [Describe changes made]"
git push
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.
- 6d ago First seen · 93 lines · 13 tokens per session scan A 5178f609cb80
check-pr-feedback is a command published in the GitHub repository deslicer/mcp-for-splunk (27 stars, last pushed 3d ago), licensed Apache-2.0. It adds 13 tokens to every session and 695 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-30.
Other commands, from other repositories
devkit.github.review-pr
Provides comprehensive GitHub pull request review with code quality, security, and best practices analysis. Use when reviewing a PR before merging.
speckit.spex.submit
Push and create PR for team review, with optional watch mode for CI monitoring.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
code-review
Code review for branch changes. Analyzes git diff between branches with multi-level depth (low/medium/high). Matches changes against task description. Returns structured report with severity levels and verdict.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
advanced-code-review-context
Advanced Code Review Phase 2: Context Analysis - load previous reviews, PR history, declined items.