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 agentmods add skills/dorayo/orchestrix-skills/commitnpx skills add dorayo/orchestrix-skills --skill commitgit clone --depth 1 https://github.com/dorayo/orchestrix-skillsWrote 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/dorayo/orchestrix-skills/commit)<a href="https://agentmods.dev/skills/dorayo/orchestrix-skills/commit"><img src="https://agentmods.dev/badge/skills/dorayo/orchestrix-skills/commit.svg" alt="Measured on agentmods" 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 | $0.00015 | $0.00529 |
| Opus 5 | $0.00008 | $0.00264 |
| Sonnet 5 | $0.00003 | $0.00106 |
| Haiku 4.5 | $0.00002 | $0.00053 |
Grade A, and why
commit 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 3d 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.
What it actually says
Commit
Record verified work as one conventional commit.
Core principle: Commit only what is verified. Never commit to claim progress.
Preconditions
run-testsis green (run it now if unsure; do not trust a remembered run).- You are NOT on the default branch (
main/master). If you are, stop and ask. - The staged change matches
message_intent— reviewgit diff --stagedfirst.
Steps
- Stage only the intended files:
git add <paths>. Nevergit add .blindly. - Confirm the staged diff:
git diff --staged. - Confirm nothing forbidden is staged: no
dist/, no build artifacts, no secrets, no.env*. - Commit with the message format below.
Message format
A conventional-commit subject, optional body, and whatever trailer this project requires:
<type>(<scope>): <summary>
<optional body>
<project-required trailer, if any>
<type>: feat | fix | refactor | docs | test | chore | …- The project decides the trailer, and it is binding. Look for a required
commit trailer in
CLAUDE.md/AGENTS.md/ contributing docs / a commit hook, and reproduce it EXACTLY — a hook that enforces one will reject the commit otherwise, and a near-miss costs a rewrite. If the project defines none, write no trailer. - Never invent a trailer, and never add
Co-Authored-Byor a tool-attribution footer the project did not ask for. Whose name ends up in a project's history is the project's call, not this skill's.
Done
Output the commit SHA and subject. Do not push.
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.
- 3d ago First seen · 66 lines · 15 tokens per session scan A 43f8f1212797
commit is a skill published in the GitHub repository dorayo/orchestrix-skills (2 stars, last pushed 3d ago), licensed MIT. It adds 15 tokens to every session and 529 once invoked, about $0.0001 per session on Opus 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
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
commits
Use this skill whenever the user asks to commit changes, write or fix a commit message, amend or rename a commit, or do a workflow that includes committing in the IntelliJ repository. This is a thin repo-specific overlay: use IntelliJ commit format, write full commit messages by default, and keep requested suffixes…
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…
commit
Commit current changes with a clear, descriptive message.
git-master
MUST USE whenever a task needs a commit or git-history investigation. Covers atomic commits, staging, commit-message style, rebase, squash, fixup/autosquash, blame, bisect, reflog, git log -S/-G, and questions like who wrote this or when was this added. Do not use for ordinary code edits unless the user asks for git…