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 Muriel-Salvan/x_aeon_agents --skill implementing-github-issuegit clone --depth 1 https://github.com/Muriel-Salvan/x_aeon_agentsWrote 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/implementing-github-issue)<a href="https://agentmods.dev/skills/muriel-salvan/x_aeon_agents/implementing-github-issue"><img src="https://agentmods.dev/badge/skills/muriel-salvan/x_aeon_agents/implementing-github-issue/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/implementing-github-issue"><img src="https://agentmods.dev/badge/skills/muriel-salvan/x_aeon_agents/implementing-github-issue.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.00064 | $0.00637 |
| Opus 5.5 | $0.00026 | $0.00255 |
| Sonnet 5.5 | $0.00013 | $0.00127 |
| Haiku 4.5 | $0.00006 | $0.00064 |
Grade A, and why
implementing-github-issue 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implementing a GitHub issue
Sequential steps to be followed when using this skill
When implementing a GitHub issue, follow those steps.
Create the implementing-github-issue Execution Checklist (MANDATORY)
- Before executing anything, create a checklist named implementing-github-issue Execution Checklist with all steps of these instructions.
- The implementing-github-issue Execution Checklist must include all numbered steps explicitly.
- After completing each step of these instructions, mark the item in the implementing-github-issue 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 implementing-github-issue Execution Checklist remains open.
1. Inform the user
- Always tell the user "SKILL: I am implementing a GitHub issue" to inform the user that you are running this skill.
2. Analyze the GitHub issue requirements to get an implementation plan (can be done when in Plan mode)
- Always use
skill: analyzing-github-issueto get a full implementation plan. This plan will take into consideration requirements from the issue, user inputs and the project's context.
3. Implement the issue following the implementation plan
- Always perform all the agreed steps from the implementation plan to implement the issue.
- Always perform a final verification of the implementation plan against all the actions you did. If you think some steps of the implementation plan were not implemented properly or are missing, fix it or inform the user about those missing steps.
4. Validate all production quality checks
- Always use
skill: validating-production-qualitybefore attempting task completion to make sure that all needed quality gates are passing.
Final Verification (MANDATORY)
Before declaring the task complete:
- Re-list all numbered steps from the implementing-github-issue Execution Checklist.
- Confirm each one was executed.
- If any step was not executed, execute it now.
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 · 66 lines · 64 tokens per session scan A 6649c2b49ba5
implementing-github-issue 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 64 tokens to every session and 637 once invoked, about $0.0003 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.