Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Muriel-Salvan/x_aeon_agentsnpx agentmods add skills/muriel-salvan/x_aeon_agents/creating-pull-requestWrote 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/muriel-salvan/x_aeon_agents/creating-pull-request)<a href="https://agentmods.dev/skills/muriel-salvan/x_aeon_agents/creating-pull-request"><img src="https://agentmods.dev/badge/skills/muriel-salvan/x_aeon_agents/creating-pull-request/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/muriel-salvan/x_aeon_agents/creating-pull-request"><img src="https://agentmods.dev/badge/skills/muriel-salvan/x_aeon_agents/creating-pull-request.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.01080 |
| Opus 5.5 | $0.00016 | $0.00432 |
| Sonnet 5.5 | $0.00008 | $0.00216 |
| Haiku 4.5 | $0.00004 | $0.00108 |
Grade A, and why
creating-pull-request 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 2mo 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Creating a Pull Request
Sequential steps to be followed when using this skill
When creating a Pull Request, follow those steps.
Create the creating-pull-request Execution Checklist (MANDATORY)
- Before executing anything, create a checklist named creating-pull-request Execution Checklist with all steps of these instructions.
- The creating-pull-request Execution Checklist must include all numbered steps explicitly.
- After completing each step of these instructions, mark the item in the creating-pull-request Execution Checklist as completed.
- Do not skip any item.
- If an item cannot be executed, explicitly explain why.
- Never mark the task as completed while any item from the creating-pull-request Execution Checklist remains open.
1. Inform the user
- Always tell the user "SKILL: I am creating a Pull Request" to inform the user that you are running this skill.
2. Ask the user about additional list of GitHub issues linked to this Pull Request
- Always use
agent: ask_followup_questionto ask the user which GitHub issues are closed by or related to this Pull Request, even if you know of some of those issues already. There could be more GitHub issues that you are not aware of.
3. Devise the list of GitHub issues linked to this Pull Request
- Use the information from all the user prompts to know which additional issues are closed by or related to this Pull Request.
4. Create a temporary file with a good description for the Pull Request
- Always devise a meaningful Pull Request description for all the changes that you have in the current branch, and for the task you want to achieve in this branch.
- Always add a section in the Pull Request description that lists all GitHub issues closed by or related to this Pull Request (devised in step 2), with mentions like "Closes #{issue_id}" or "Relates to #{issue_id}".
- Always add a section in the Pull Request description that contains the exact initial prompt of the user for this task, and all user inputs or precisions that you have received from the user while implementing the task.
- Always use
agent: write_to_filetool to write the devised Pull Request description in a temporary file (later referenced as {pr_description_file}), inside the directory.x_aeon_agents/tmp/prs.
What ships with it
1 file 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.
- 2mo ago First seen · 108 lines · 39 tokens per session scan A 4ecced172646
creating-pull-request is a skill published in the GitHub repository Muriel-Salvan/x_aeon_agents (2 stars, last pushed 3d ago), licensed BSD-3-Clause. It adds 39 tokens to every session and 1,080 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-31.
Other skills, from other repositories
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.