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 skills add lwalden/AIAgentMinder --skill pr-pipelinegit clone --depth 1 https://github.com/lwalden/AIAgentMinderWrote 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/lwalden/aiagentminder/pr-pipeline)<a href="https://agentmods.dev/skills/lwalden/aiagentminder/pr-pipeline"><img src="https://agentmods.dev/badge/skills/lwalden/aiagentminder/pr-pipeline/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/skills/lwalden/aiagentminder/pr-pipeline"><img src="https://agentmods.dev/badge/skills/lwalden/aiagentminder/pr-pipeline.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.00012 | $0.04579 |
| Opus 5 | $0.00006 | $0.02289 |
| Sonnet 5 | $0.00002 | $0.00916 |
| Haiku 4.5 | $0.00001 | $0.00458 |
Grade A, and why
pr-pipeline scanned grade A with 1 finding 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 9d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- HTTP endpoints: use `curl` or `Invoke-WebRequest` How it starts
The opening of the file, as written. The whole thing — 592 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/aiagentminder:pr-pipeline - Autonomous PR Review Pipeline
Review, fix, test, and merge a pull request autonomously. Handles the full review→fix→test→merge loop with human escalation for high-risk or genuinely blocked cases.
Invoked in-session by the sprint workflow after PR creation, or manually:
/aiagentminder:pr-pipeline (uses current branch PR) or /aiagentminder:pr-pipeline <PR-URL>.
Step 0: Parse Input and Load Config
Determine the PR:
If invoked with a PR URL argument: parse owner, repo, and PR number.
If invoked without arguments, get current PR:
git rev-parse --abbrev-ref HEAD
gh pr view --json number,url,headRefName,baseRefName,title,body,author
If no open PR for the current branch, tell the user and stop.
Load config from .pr-pipeline.json at the repo root (if it exists):
{
"highRiskPatterns": ["**/auth/**", "**/security/**", "**/payment/**",
"**/billing/**", "**/migration/**", ".github/workflows/**",
"Dockerfile*", "docker-compose*", "*.tf", "*.tfvars"],
"cycleLimit": 5,
"autoMerge": true,
"mergeMethod": "squash",
"skipPatterns": ["package-lock.json", "yarn.lock", "*.lock",
"dist/**", "build/**", ".next/**"],
"notification": { "email": "", "from": "[email protected]" },
"testCommand": null,
"mergeWait": { "pollIntervalSeconds": 30, "timeoutMinutes": 15 }
}
If the file is absent, use these defaults.
Get PR metadata:
gh pr view {number} --json number,title,body,headRefName,baseRefName,files,labels,headRefOid,author
Initialize cycle counter: Check PR labels for a label matching ai-cycle-N.
Set cycleNumber to N, or 1 if no such label exists.
Step 1: High-Risk File Gate
Get the list of changed files from the PR metadata (Step 0, files field).
Check each file path against highRiskPatterns. Use glob-style matching:
** matches any path segment, * matches within a single segment.
If ANY file matches a high-risk pattern:
- Comment on the PR:
## PR Pipeline — Human Review Required This PR modifies files in a high-risk area that requires human review before automated processing: {list each matching file and which pattern it matched} The pipeline has stopped. Please review and merge manually, or remove the relevant files from the PR if the change is unintentional.gh pr comment {number} --body "..."
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.
- 9d ago First seen · 592 lines · 12 tokens per session scan A 2fe40f8637fe
pr-pipeline is a skill published in the GitHub repository lwalden/AIAgentMinder (5 stars, last pushed 1mo ago), licensed MIT. It adds 12 tokens to every session and 4,579 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
github-commenting
How to post clean, rich, deduplicated GitHub PR review comments — suggestion blocks, multi-line anchors, markers, formatting rules. Load before posting or fixing any PR comment.
joycraft-spec-done
Lightweight per-spec wrap-up — bump status to in-review, terse discovery if surprised, commit. Run after each spec in checkpoint/isolated mode; no validation, no push, no PR.
mx-pr
Draft a pull request from the feature spec and git log, run an autonomous commit-history cleanup (content check), then publish to GitHub or GitLab (Bitbucket experimental) — or hand off. Use when a feature branch is ready for PR, standalone or from mx-flow. Usage: /mx-pr [name].
mx-commit
Commit all pending changes as one commit per logical concern, following the project's message convention (type prefix, 50-char subject, English). Use when the working tree may hold several changes or the convention must be enforced; a single trivial change can use plain git commit. Usage: /mx-commit [--auto].
bmad-loop
Iterate over a list of story keys, executing dev → review → PR → CI → merge for each. Use when the user says "loop these stories [list]" or "run the loop on [story keys]".
codex-oss-maintainer-toolkit
Build Codex-native workflows for open-source maintenance. Use when creating AGENTS.md guidance, maintainer skills, issue triage flows, PR review prompts, release-note routines, or repository verification scripts.