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 joaquimscosta/arkhe-claude-plugins --skill creating-prgit clone --depth 1 https://github.com/joaquimscosta/arkhe-claude-pluginsWrote 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/joaquimscosta/arkhe-claude-plugins/creating-pr)<a href="https://agentmods.dev/skills/joaquimscosta/arkhe-claude-plugins/creating-pr"><img src="https://agentmods.dev/badge/skills/joaquimscosta/arkhe-claude-plugins/creating-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/skills/joaquimscosta/arkhe-claude-plugins/creating-pr"><img src="https://agentmods.dev/badge/skills/joaquimscosta/arkhe-claude-plugins/creating-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.00103 | $0.03549 |
| Opus 5.5 | $0.00041 | $0.01420 |
| Sonnet 5.5 | $0.00021 | $0.00710 |
| Haiku 4.5 | $0.00010 | $0.00355 |
Grade A, and why
creating-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 yesterday.
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 — 460 lines — stays where its author put it; the contents beside it link to each section on GitHub.
⚠️ CRITICAL CONSTRAINTS
No Claude Code Footer Policy
YOU MUST NEVER add Claude Code attribution to pull requests.
- ❌ NO "🤖 Generated with [Claude Code]" in PR titles or descriptions
- ❌ NO "Co-Authored-By: Claude [email protected]" in PR content
- ❌ NO Claude Code attribution, footer, or branding of any kind
Pull requests are public code review documents and must remain clean and professional.
GitHub PR Creation Workflow
Execute GitHub Pull Request workflows with automatic repository detection, branch management, and intelligent PR content generation.
Usage
This skill is invoked when:
- User runs
/create-pror/git:create-prcommand - User requests to create a pull request
- User asks to open a PR or push changes for review
How It Works
This skill handles the complete PR workflow:
- Repository Detection - Detect current repository context (root or submodule)
- Branch Validation - Verify not on protected branch, check for uncommitted changes
- Branch Pushing - Ensure branch exists on remote
- Existing PR Detection - Check if PR already exists for current branch
- PR Content Generation - Create title and description from commits
- PR Creation - Create or update PR using GitHub CLI
Supported Arguments
Parse arguments from user input:
- No arguments: Auto-detect repository and create PR to main branch
<scope>: Direct PR for specific repository (root, submodule-name)--draft: Create as draft PR--base <branch>: Target branch (default: main)- Combinations:
<scope> --draft,root --base staging, etc.
Prerequisites
GitHub CLI Required: Must have gh installed and authenticated
# Install GitHub CLI (if not installed)
# macOS: brew install gh
# Linux: See https://cli.github.com/
# Authenticate
gh auth login
PR Creation Workflow Steps
Step 1: Parse Arguments
Extract scope, draft flag, and base branch from user input:
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 460 lines · 103 tokens per session scan A 835ff35a6bdc
creating-pr is a skill published in the GitHub repository joaquimscosta/arkhe-claude-plugins (21 stars, last pushed yesterday), licensed MIT. It adds 103 tokens to every session and 3,549 once invoked, about $0.0004 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-10-16.
Other skills, from other repositories
pr-creator
Create well-structured pull requests with proper descriptions and labels.
dev-rc
The last gate before merge — QA, security audit, review and changelog, with objective pass conditions.
pr-autofix
When the user has PR review feedback to address, CI failures to fix, or wants to automatically resolve common PR issues. Use when the user says "fix the PR," "address review comments," "CI is failing," "fix the build," "autofix," "pr feedback," "resolve comments," "fix merge conflicts," or when a PR needs updates…
babysit
Watch a pull request or review cycle until it is ready to merge. Use when asked to babysit, monitor, or keep checking PR comments, reviews, and CI until all actionable issues are resolved.
github
GitHub via gh CLI: PRs, issues, reviews, repos, auth.
feedback-builder
Point Aeon at a service's /feedback endpoint - pull what agents reported (bugs, missing features), triage and cluster it, then build the best accepted request as a PR for a human to approve.