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 commands/vishnu2kmohan/mcp-server-langgraph/pr-checksgit clone --depth 1 https://github.com/vishnu2kmohan/mcp-server-langgraphWrote 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/vishnu2kmohan/mcp-server-langgraph/pr-checks)<a href="https://agentmods.dev/commands/vishnu2kmohan/mcp-server-langgraph/pr-checks"><img src="https://agentmods.dev/badge/commands/vishnu2kmohan/mcp-server-langgraph/pr-checks.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.00006 | $0.03529 |
| Opus 5 | $0.00003 | $0.01765 |
| Sonnet 5 | $0.00001 | $0.00706 |
| Haiku 4.5 | $0.00001 | $0.00353 |
Grade A, and why
pr-checks 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 5d 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 — 572 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Checks Summary
Usage: /pr-checks or /pr-checks <pr-number>
Purpose: Comprehensive Pull Request validation summary
🔍 What This Command Does
Shows complete PR validation status including:
- Required checks status (passing/failing/pending)
- Review approval status
- Merge conflicts status
- PR size and complexity metrics
- CI/CD workflow results
- Code coverage impact
📊 PR Validation Workflow
Step 1: Identify Pull Request
Determine which PR to check:
# If PR number provided
if [ -n "$ARGUMENTS" ]; then
PR_NUMBER="$ARGUMENTS"
else
# Get PR for current branch
PR_NUMBER=$(gh pr view --json number --jq '.number' 2>/dev/null)
if [ -z "$PR_NUMBER" ]; then
echo "No PR found for current branch"
echo "Create PR with: gh pr create"
exit 1
fi
fi
echo "Checking PR #$PR_NUMBER"
Step 2: Fetch PR Information
Get comprehensive PR details:
# Get PR metadata
gh pr view $PR_NUMBER --json \
number,title,state,isDraft,mergeable,reviewDecision,\
statusCheckRollup,additions,deletions,changedFiles,\
url,baseRefName,headRefName,author,createdAt,updatedAt
# Example output structure:
# {
# "number": 123,
# "title": "feat: add session management",
# "state": "OPEN",
# "isDraft": false,
# "mergeable": "MERGEABLE",
# "reviewDecision": "APPROVED",
# "statusCheckRollup": [...]
# "additions": 450,
# "deletions": 120,
# "changedFiles": 8
# }
Step 3: Check Required Status Checks
Analyze CI/CD check status:
# Parse status checks
gh pr view $PR_NUMBER --json statusCheckRollup \
--jq '.statusCheckRollup[] | {name: .name, status: .status, conclusion: .conclusion}'
# Group by status
PASSING=$(gh pr view $PR_NUMBER --json statusCheckRollup \
--jq '[.statusCheckRollup[] | select(.conclusion=="SUCCESS")] | length')
FAILING=$(gh pr view $PR_NUMBER --json statusCheckRollup \
--jq '[.statusCheckRollup[] | select(.conclusion=="FAILURE")] | length')
PENDING=$(gh pr view $PR_NUMBER --json statusCheckRollup \
--jq '[.statusCheckRollup[] | select(.status=="PENDING")] | length')
TOTAL=$(gh pr view $PR_NUMBER --json statusCheckRollup --jq '.statusCheckRollup | length')
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.
- 5d ago First seen · 572 lines · 6 tokens per session scan A 64aa2c0255c1
pr-checks is a command published in the GitHub repository vishnu2kmohan/mcp-server-langgraph (4 stars, last pushed 11d ago), licensed MIT. It adds 6 tokens to every session and 3,529 once invoked, about $0.0000 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 commands, from other repositories
hal-voice-toggle
Toggle HAL 9000 voice clips on or off.
deps-age
Analyze dependency freshness and maintenance activity.
OPSX: Bulk Archive
Archive multiple completed changes at once.
designer
UI/UX design with Memory coordination for consistent experiences.
reviewer
Code review using batch file analysis for comprehensive reviews.
pipeline-generate
You are a senior DevOps & Cloud Infrastructure specialist. The user needs help with pipeline generate in the context of ci/cd pipelines, container orchestration, iac, monitoring and incident response.