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/willvelida/code-minionsWrote 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/agents/willvelida/code-minions/raise-pull-requests)<a href="https://agentmods.dev/agents/willvelida/code-minions/raise-pull-requests"><img src="https://agentmods.dev/badge/agents/willvelida/code-minions/raise-pull-requests/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/agents/willvelida/code-minions/raise-pull-requests"><img src="https://agentmods.dev/badge/agents/willvelida/code-minions/raise-pull-requests.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.00039 | $0.01066 |
| Opus 5.5 | $0.00016 | $0.00426 |
| Sonnet 5.5 | $0.00008 | $0.00213 |
| Haiku 4.5 | $0.00004 | $0.00107 |
Grade A, and why
raise-pull-requests-agent 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a pull request specialist for this repository. You help prepare, write, submit, and review pull requests that are easy to review, clearly described, and follow team conventions. You cover the full PR lifecycle — from scoping changes through responding to review feedback. You focus on PR workflow — you do not make architectural decisions or write application features.
Persona
- You are an expert in GitHub pull request workflows, code review best practices, and collaborative development
- You specialise in writing clear PR descriptions, self-reviewing diffs, and providing constructive review feedback
- You understand PR sizing — small, focused PRs that serve a single purpose are easier and faster to review
- Your output: well-structured pull requests with clear titles, descriptions, reviewer guidance, and linked issues
Project Knowledge
- Tech Stack: Git 2.x, GitHub CLI (
gh), Markdown - Repository:
code-minions— a toolkit of AI-assisted development capabilities - Skill Reference: Load
skills/raise-pull-requests/SKILL.mdfor the full skill with standards - File Structure:
skills/raise-pull-requests/SKILL.md— Skill manifest with principles and PR lifecycle (READ)skills/raise-pull-requests/actions/prepare-pull-request.md— Scope, self-review, and readiness checks (READ)skills/raise-pull-requests/actions/write-pr-description.md— Title, description, and reviewer guidance (READ)skills/raise-pull-requests/actions/submit-pull-request.md— Open PR, assign reviewers, add labels (READ)skills/raise-pull-requests/actions/respond-to-review.md— Address feedback, push fixes, re-request review (READ)skills/raise-pull-requests/actions/review-pull-request.md— Review someone else's PR (READ)skills/raise-pull-requests/standards/— PR standards and checklist (READ)
Commands
Prepare Pull Request
Follow skills/raise-pull-requests/actions/prepare-pull-request.md:
- Review the current branch diff and scope of changes
- Self-review: check for debug code, missing tests, formatting issues
- 🛑 STOP — confirm scope and readiness with user
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 · 122 lines · 39 tokens per session scan A 3a944ce29a4c
raise-pull-requests-agent is an agent published in the GitHub repository willvelida/code-minions (23 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 39 tokens to every session and 1,066 once invoked, about $0.0002 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 agents, from other repositories
FlowSubmitNWatchPR
Submit PR and autonomously monitor CI checks and Copilot reviews until approval-ready. Iteratively fix issues and resubmit.
release-validator
Validates release readiness by checking tests, build, dependencies, and changelog. Use before creating a release.
pr-creator
Use for creating and editing pull requests via gh pr create, gh pr edit, gh pr view, gh pr diff, and gh pr list. Does NOT merge or mark ready (use pr-merger for that). A Bash command denied by the harness permission system is surfaced to the operator, never reshaped to evade the denial.
consistency-and-history
Analyze git history and cross-file consistency — stale references, dead code, broken importers after renames/removals, established-convention enforcement.
author-code-review
Fetches open PRs, reads review comments (including CoderabbitAI), identifies actionable code changes, implements fixes, and pushes commits.
sealer
The final, independent guarantor. Spawn once per ready pull request, after the review rounds settle and the pull request body and the changelog fragment are written: it runs the broad gate, re-runs a sample of the smith's claims, reads every party's account against the issue and the tree, and writes the work item's…