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/KaelSensei/MagicAIBuilderWrote 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/kaelsensei/magicaibuilder/add-commit-push)<a href="https://agentmods.dev/commands/kaelsensei/magicaibuilder/add-commit-push"><img src="https://agentmods.dev/badge/commands/kaelsensei/magicaibuilder/add-commit-push/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/kaelsensei/magicaibuilder/add-commit-push"><img src="https://agentmods.dev/badge/commands/kaelsensei/magicaibuilder/add-commit-push.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.00000 | $0.00990 |
| Opus 5.5 | $0.00000 | $0.00396 |
| Sonnet 5.5 | $0.00000 | $0.00198 |
| Haiku 4.5 | $0.00000 | $0.00099 |
Grade A, and why
add-commit-push 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Command – Stage, Commit, and Push Current Changes
When /git [message] is invoked, immediately execute the following steps to stage changes, create a
conventional commit, and push to the current branch.
Step 1: Load Project Context & Follow All Rules
- Assume the project root as the working directory
- Load and strictly follow ALL Cursor rules from
.cursor/rules/*.mdc:security.mdc- Security requirementsdocumentation.mdc- Documentation update requirementsversion-management.mdc- Git workflow and commit conventionsgeneral-principles.mdc- Project philosophy (keep it simple)
- Read relevant documentation if present:
README.md- Project progress / changelog docs (e.g.,
PROGRESS.md,CHANGELOG.md)
Step 2: Safety Checks (Mandatory)
-
Check current branch:
git branch --show-current -
Refuse to commit directly to protected branches:
- If branch is
mainormaster, stop and ask the user to create a feature branch first.
- If branch is
-
Check working tree:
git status -
If there is nothing to commit, report that and stop.
Step 3: Run Project Checks (Lint / Format / Tests)
Before committing, run the project's standard checks if they exist:
-
Detect common check commands by looking for scripts and config files:
- Node:
package.jsonscripts likecheck,lint,format:check,test - Python:
pyproject.toml,pytest.ini,ruff.toml - Go:
go test ./...,golangci-lint run - Rust:
cargo test,cargo fmt --check,cargo clippy
- Node:
-
Run the most relevant, fastest checks first (format check + lint).
-
If checks fail:
- Stop and report the failures
- Fix if safe and straightforward
- Re-run the checks until they pass
Note: if the repo has a pre-commit hook, it will also run automatically when committing.
Step 3.5: SonarCloud Quality Gate (Mandatory)
After the code is ready and the tests pass, run the Sonar scan and verify there are 0 open issues.
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 · 149 lines · 0 tokens per session scan A ec6680522191
add-commit-push is a command published in the GitHub repository KaelSensei/MagicAIBuilder (2 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 990 tokens. 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 commands, from other repositories
speckit.git.commit
Proxy for speckit.git.commit.md.
scm
SCM workflow for Git operations (branching/merge/conflict/worktree) plus Conventional Commit execution.
review-diff
Round 1 review - fan out correctness, security, and invariant lanes over a git range and write local://review-findings.md.
review-fixes
Round 2 review - verify each finding is actually resolved and hunt regressions introduced by the fixes.
git-commit
Commit and push changes in the current or a specified directory.
gnite
Wrap up the session: commit, push, reap, hand off.