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.
git clone --depth 1 https://github.com/giuseppe-trisciuoglio/developer-kitWrote 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/giuseppe-trisciuoglio/developer-kit/devkit.github.review-pr)<a href="https://agentmods.dev/commands/giuseppe-trisciuoglio/developer-kit/devkit.github.review-pr"><img src="https://agentmods.dev/badge/commands/giuseppe-trisciuoglio/developer-kit/devkit.github.review-pr/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/giuseppe-trisciuoglio/developer-kit/devkit.github.review-pr"><img src="https://agentmods.dev/badge/commands/giuseppe-trisciuoglio/developer-kit/devkit.github.review-pr.svg" alt="Reviewed on agentmods" width="80" 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.00026 | $0.04099 |
| Opus 5.5 | $0.00010 | $0.01640 |
| Sonnet 5.5 | $0.00005 | $0.00820 |
| Haiku 4.5 | $0.00003 | $0.00410 |
Grade A, and why
devkit.github.review-pr 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 1mo 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 — 653 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Pull Request Comprehensive Review
Overview
Perform comprehensive code review of a GitHub pull request including code quality, security, architecture, performance, and best practices analysis.
Overview
- Title: $PR_TITLE
- Author: $PR_AUTHOR
- Branch: $PR_HEAD → $PR_BASE
- Changes: +$PR_ADDITIONS -$PR_DELETIONS across $PR_CHANGED_FILES files
- Review Focus: $REVIEW_FOCUS
Usage
/devkit.github.review-pr $ARGUMENTS
Arguments
| Argument | Description |
|---|---|
$ARGUMENTS |
Combined arguments passed to the command |
Current Context
- Current Branch: !
git branch --show-current - Remote Repository: !
git config --get remote.origin.url - Git Status: !
git status --porcelain
Execution Instructions
Agent Selection: To execute this GitHub task, use the following approach:
- Primary: Use
general-purposeagent with GitHub CLI expertise and code analysis capabilities
Configuration
Arguments received: $ARGUMENTS
$1: PR number (required - e.g., 123)
$2: Review focus (optional - defaults to full)
$3: Output format (optional - defaults to summary)
Available review focuses:
full- Complete comprehensive review (default)security- Security vulnerabilities and risks onlyperformance- Performance bottlenecks and optimizationsarchitecture- Design patterns and architectural decisionstesting- Test coverage and qualitystyle- Code style and conventions
Output formats:
summary- Concise executive summary (default)detailed- Comprehensive detailed reportchecklist- Review checklist formatissues- GitHub issues-ready format
Phase 1: PR Information Extraction
1.1 Fetch PR Details
# Validate PR number
if [ -z "$1" ]; then
echo "Error: PR number is required"
echo "Usage: /developer-kit:devkit.github.review-pr <pr-number> [review-focus] [output-format]"
exit 1
fi
PR_NUMBER=$1
REVIEW_FOCUS=${2:-full}
OUTPUT_FORMAT=${3:-summary}
# Check GitHub CLI authentication
if ! gh auth status > /dev/null 2>&1; then
echo "Error: GitHub CLI not authenticated. Run: gh auth login"
exit 1
fi
# Fetch PR information
echo "Fetching PR #$PR_NUMBER details..."
PR_TITLE=$(gh pr view $PR_NUMBER --json title -q .title)
PR_AUTHOR=$(gh pr view $PR_NUMBER --json author -q .author.login)
PR_STATE=$(gh pr view $PR_NUMBER --json state -q .state)
PR_BASE=$(gh pr view $PR_NUMBER --json baseRefName -q .baseRefName)
PR_HEAD=$(gh pr view $PR_NUMBER --json headRefName -q .headRefName)
PR_URL=$(gh pr view $PR_NUMBER --json url -q .url)
PR_CREATED=$(gh pr view $PR_NUMBER --json createdAt -q .createdAt)
PR_ADDITIONS=$(gh pr view $PR_NUMBER --json additions -q .additions)
PR_DELETIONS=$(gh pr view $PR_NUMBER --json deletions -q .deletions)
PR_CHANGED_FILES=$(gh pr view $PR_NUMBER --json changedFiles -q .changedFiles)
echo "PR Title: $PR_TITLE"
echo "Author: $PR_AUTHOR"
echo "State: $PR_STATE"
echo "Branch: $PR_HEAD -> $PR_BASE"
echo "Changes: +$PR_ADDITIONS -$PR_DELETIONS across $PR_CHANGED_FILES files"
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.
- 1mo ago First seen · 653 lines · 26 tokens per session scan A 266fc7f104a6
devkit.github.review-pr is a command published in the GitHub repository giuseppe-trisciuoglio/developer-kit (359 stars, last pushed 1mo ago), licensed MIT. It adds 26 tokens to every session and 4,099 once invoked, about $0.0001 per session on Opus 5.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
pr-enhance
Command "pr-enhance" from smith-horn/skillsmith, covering pr-enhance, usage, options, examples and fetch/manage pr data via the cli escape hatch.
pr-enhance
Command "pr-enhance" from dp-web4/SAGE, covering pr-enhance, usage, options, examples and enhance pr.
pr
Create a GitHub PR from current branch with unpushed commits — discovers templates, analyzes changes, pushes.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.