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 commands/fusengine/agents/commitgit clone --depth 1 https://github.com/fusengine/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/commands/fusengine/agents/commit)<a href="https://agentmods.dev/commands/fusengine/agents/commit"><img src="https://agentmods.dev/badge/commands/fusengine/agents/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.00031 | $0.02840 |
| Opus 5 | $0.00015 | $0.01420 |
| Sonnet 5 | $0.00006 | $0.00568 |
| Haiku 4.5 | $0.00003 | $0.00284 |
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 yesterday.
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 — 271 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Smart Conventional Commit
Current State
!git status
Staged Changes
!git diff --staged --stat
Recent Commits (style reference)
!git log --oneline -5
Current Branch
!git branch --show-current
Instructions
Based on the context above, create a professional commit.
Step 0: Branch Check (GitHub Flow enforcement)
Read current branch from above.
If current branch is main, master, develop, or production:
BLOCK direct commits and propose a feature branch:
🌿 Branch Protection
───────────────────────────────
Current: <branch>
Issue: Direct commits to protected branches discouraged (GitHub Flow)
───────────────────────────────
Pre-detect commit type/scope from staged changes (Step 2 logic) to suggest branch name:
- feat(seo) → feat/seo
- fix(sniper) → fix/sniper
- chore(deps) → chore/deps
Proposed branch: <type>/<scope-or-summary>
Options:
Y → Create branch + continue commit
N → Abort
C → Custom branch name
If user accepts → execute git checkout -b <branch> then proceed to Step 1.
If user declines → STOP, do not commit.
If current branch already a feature branch (e.g. feat/*, fix/*, chore/*, docs/*, refactor/*, perf/*, test/*, ci/*, build/*, style/*) → skip to Step 1 directly.
Exceptions (allow direct commit on main):
- Repo has only
mainbranch and no remote (solo prototype) - User explicitly passes
--no-branch-checkin$ARGUMENTS - Commit type is
choreAND scope isreleaseorversion(post-commit bump commits)
Step 1: Security Check
BLOCK and output if secrets detected:
🔒 Security Alert
───────────────────────────────
Found: [file or pattern]
Action: Commit blocked
Fix: Remove sensitive data before committing
Check for:
.env,.env.*files- Patterns:
password=,secret=,api_key=,token= - Files:
*.pem,*.key,*credentials*
Step 2: Analyze and Detect
Output analysis:
📊 Analysis
───────────────────────────────
Files changed: [X]
Files staged: [Y]
Pattern detected: [type]
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.
- yesterday First seen · 271 lines · 31 tokens per session scan A 19f6bd3c637a
commit is a command published in the GitHub repository fusengine/agents (25 stars, last pushed 1mo ago), licensed MIT. It adds 31 tokens to every session and 2,840 once invoked, about $0.0002 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-09-03.
Other commands, from other repositories
ship
Branch, commit, open PR, gather Claude + every enabled AI reviewer (Copilot, CodeRabbit, etc.), fix/justify/resolve every finding, loop until clean, then merge. Run only when implementation is finished AND the owner has said to ship (e.g. "ship it") — never self-invoke just because the work looks done. To design and…
flow
Universal workflow entry point. Use /flow for skill-driven GitHub development. Verbs: start, commit, pr, review, address, merge, resolve, release, status, learn, setup, explain, debug, design, brainstorm, issue.
ship
Use after audit returns Verdict PASS. Atomic git commit + tag + ledger update. Single-writer; cannot fan-out.
push
Commit, push, and post a progress comment using session context or branch detection.
ship
Commit changes, push, and create PR.
ship
Deliver the finished change as a Conventional Commit, branch and PR; release cuts a version instead.