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/oodaris/autocodex/eng-conventional-commit-helpernpx skills add oodaris/autocodex --skill eng-conventional-commit-helpergit clone --depth 1 https://github.com/oodaris/autocodexWrote 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/oodaris/autocodex/eng-conventional-commit-helper)<a href="https://agentmods.dev/skills/oodaris/autocodex/eng-conventional-commit-helper"><img src="https://agentmods.dev/badge/skills/oodaris/autocodex/eng-conventional-commit-helper.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.1 | $0.00016 | $0.00229 |
| Opus 5 | $0.00008 | $0.00114 |
| Sonnet 5 | $0.00003 | $0.00046 |
| Haiku 4.5 | $0.00002 | $0.00023 |
Grade A, and why
eng-conventional-commit-helper 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 6d 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
Conventional Commit Helper
Repo anchors (autocodex)
- REPO_ROOT:
.
When to use
- Preparing commits for changes.
Preconditions
- Git working tree exists.
- No destructive git commands.
Inputs to confirm
- Intended change type (feat/fix/docs/refactor/test/chore)
- Scope (cli/plugins/api/ui/docs)
Required artifacts
- Proposed conventional commit message
- Staged file list
Quick path
- Inspect diff.
- Stage one intent.
- Commit with conventional message.
Steps
git status -sb- Stage files for one intent.
git commit -m "type(scope): subject"
Failure modes and responses
- Mixed changes: split into multiple commits.
- Generated noise: unstage or ignore.
Definition of done
- Commit is conventional and scoped.
Example (minimal)
feat(cli): add plugins command
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.
- 6d ago First seen · 46 lines · 16 tokens per session scan A ebdd074f4159
eng-conventional-commit-helper is a skill published in the GitHub repository oodaris/autocodex (16 stars, last pushed 6mo ago), licensed MIT. It adds 16 tokens to every session and 229 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-30.
Other skills, from other repositories
moai-ref-git-workflow
Git workflow patterns, branch strategies, conventional commits, and PR templates reference for git operations. Agent-extending skill that amplifies manager-git expertise with production-grade git workflow patterns. NOT for: code implementation, testing, architecture design, documentation content.
git-commit-helper
Generate conventional commit messages automatically. Use when user runs git commit, stages changes, or asks for commit message help. Analyzes git diff to create clear, descriptive conventional commit messages. Triggers on git commit, staged changes, commit message requests.
private-github-search
Full-text search across all of the user's GitHub repos (including private ones) using a local mirror and ripgrep. Use for "where did I put X", "which repo has X", or any search spanning the user's repos - gh search code / the REST API cannot reliably search private repos.
intuitive-squash
Squash local GSD or agent-generated commit history into a clean, reviewable story while preserving important fixes. Use when the user asks to squash commits, clean git history, compress phase commits, prepare a branch before PR, compare aggressive vs moderate squash options, or preserve hotfix/security commits during…
shared-tooling-git-hooks
Husky v9 setup, lint-staged v16 patterns, commitlint with conventional commits, CI/production handling, monorepo setup, migration from v8.
ase-meta-commit
Determine commit message for staged Git changes.