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.
git clone --depth 1 https://github.com/allisoneer/agentic_auxilaryWrote 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/commands/allisoneer/agentic_auxilary/commit)<a href="https://agentmods.dev/commands/allisoneer/agentic_auxilary/commit"><img src="https://agentmods.dev/badge/commands/allisoneer/agentic_auxilary/commit/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/commands/allisoneer/agentic_auxilary/commit"><img src="https://agentmods.dev/badge/commands/allisoneer/agentic_auxilary/commit.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.00020 | $0.00716 |
| Opus 5.5 | $0.00008 | $0.00286 |
| Sonnet 5.5 | $0.00004 | $0.00143 |
| Haiku 4.5 | $0.00002 | $0.00072 |
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 1mo 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit Changes
You are tasked with creating git commits for the changes made during this session.
User message (if any): $ARGUMENTS
Process:
-
Think about what changed:
- Review the conversation history and understand what was accomplished
- Run
git statusto see current changes - Run
git diffto understand the modifications - Consider whether changes should be one commit or multiple logical commits
-
Determine commit type: Analyze the changes and categorize them:
feat: New feature or functionality addedfix: Bug fix or error correctionrefactor: Code restructuring without changing functionalitydocs: Documentation only changestest: Adding or updating testschore: Maintenance tasks (deps, configs, etc.)perf: Performance improvementsstyle: Formatting, missing semicolons, etc.ci: CI/CD configuration changes
-
Plan your commit(s) with conventional format:
<type>(<scope>): <description> [optional body] [optional footer(s)]- Scope is optional—use a short component, package, or directory name when it adds clarity
- For cross-cutting changes, use generic scopes like
build,deps,ci, or omit the scope entirely - Description should be imperative mood, lowercase, no period
- Body explains WHY, not what (the diff shows what)
- Footer can include
BREAKING CHANGE:for major version bumps
-
Present your plan to the user:
- List the files you plan to add for each commit
- Show the conventional commit message(s) you'll use
- Ask: "I plan to create [N] commit(s) with these changes. Shall I proceed?"
-
Execute upon confirmation:
- Use
git addwith specific files (never use-Aor.) - Create commits with your planned messages
- Show the result with
git log --oneline -n [number]
- Use
Examples:
feat(auth): add oauth callback handlerfix(cli): handle missing config file gracefullyrefactor(api): extract common request parsingdocs: document local dev setupchore(deps): bump tokio to 1.40
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.
- 1mo ago First seen · 85 lines · 20 tokens per session scan A 8418c331f8ca
commit is a command published in the GitHub repository allisoneer/agentic_auxilary (79 stars, last pushed 6d ago), licensed MIT. It adds 20 tokens to every session and 716 once invoked, about $0.0001 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-09-08.
Other commands, from other repositories
standup
Review my git commits from the past workday and generate a standup summary.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
session-report
Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
git-workflow
Run review, tests, and commit steps, then prepare a pull request.
commit
Context-aware Git commit assistant with smart pre-commit checks.