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/committing-changesWrote 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/committing-changes)<a href="https://agentmods.dev/skills/muriel-salvan/x_aeon_agents/committing-changes"><img src="https://agentmods.dev/badge/skills/muriel-salvan/x_aeon_agents/committing-changes/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/committing-changes"><img src="https://agentmods.dev/badge/skills/muriel-salvan/x_aeon_agents/committing-changes.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.00056 | $0.00855 |
| Opus 5.5 | $0.00022 | $0.00342 |
| Sonnet 5.5 | $0.00011 | $0.00171 |
| Haiku 4.5 | $0.00006 | $0.00085 |
Grade A, and why
committing-changes 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Committing changes
Sequential steps to be followed when using this skill
When committing changes, follow those steps.
Create the committing-changes Execution Checklist (MANDATORY)
- Before executing anything, create a checklist named committing-changes Execution Checklist with all steps of these instructions.
- The committing-changes Execution Checklist must include all numbered steps explicitly.
- After completing each step of these instructions, mark the item in the committing-changes 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 committing-changes Execution Checklist remains open.
1. Inform the user
- Always tell the user "SKILL: I am committing changes" to inform the user that you are running this skill.
2. Stage all the files that should be part of the commit
- Identify all the files that make sense to commit altogether as part of 1 commit.
- Always use
cli: git add {file1} {file2} ... {fileN}to stage those identified files. - Never use
cli: git add --all, because some files may be modified by the user and should not be part of your commit.
Example:
git add lib/my_lib/my_class.rb README.md
3. Create a temporary file with the commit description
- Devise a meaningful commit comment that summarizes the changes you are going to commit.
- Always use
agent: write_to_filetool to write the commit comment in a temporary file (later referenced as {description_file}), inside the directory.x_aeon_agents/tmp/commits.
4. Create the commit
- Find this skill directory path, later referenced as {skill_path}.
- Always use
cli: ruby {skill_path}/scripts/commit {description_file}to create the git commit. - Never use
cli: git commitdirectly.
Example:
ruby .cline/skills/committing-changes/scripts/commit .x_aeon_agents/tmp/commits/commit_desc.txt
5. Delete the temporary commit description file
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 · 98 lines · 56 tokens per session scan A a03e8db275db
committing-changes 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 56 tokens to every session and 855 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
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
repo-sync
Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…