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/leanandmean/mach10/pushgit clone --depth 1 https://github.com/LeanAndMean/mach10What 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.01592 |
| Opus 5 | $0.00008 | $0.00796 |
| Sonnet 5 | $0.00003 | $0.00318 |
| Haiku 4.5 | $0.00002 | $0.00159 |
Grade A, and why
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 2d 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Push
You are finalizing a batch of work: committing changes, pushing to remote, and documenting progress on the associated PR or issue.
Step 1: Determine What to Commit
Run git status and git diff --staged to understand the current state.
Staging logic:
- If you have context from this session about which files you modified, stage those specific files. Do NOT use
git add -Aorgit add .— add files by name. - If files are already staged and the staging looks correct based on session context, proceed with those.
- If it is unclear what should be staged (e.g., this is a fresh session with no prior context), review all untracked and unstaged files, present your findings to the user, and ask for guidance on what to stage.
- Never stage files that likely contain secrets (.env, credentials.json, etc.).
Step 2: Commit
Review recent commit messages for style consistency:
git log --oneline -10
Generate a commit message that:
- Follows the repository's existing commit message style
- Summarizes the nature of the changes (new feature, bug fix, refactor, etc.)
- Focuses on the "why" rather than the "what"
- If context was provided ($ARGUMENTS): if it reads like a commit message, use it verbatim; otherwise, treat it as guidance for commit message generation. Context may also inform the progress comment (Step 4) and next-step suggestions (Step 5).
Create the commit. Use a HEREDOC for the message to ensure proper formatting:
git commit -m "$(cat <<'EOF'
Commit message here.
Co-Authored-By: Claude <[email protected]>
EOF
)"
Step 3: Push
Push to the remote tracking branch:
git push
If no upstream is set, push with -u flag to the current branch name.
Step 4: Post Progress Comment
Determine the associated PR or issue using the following priority order:
1. Session context (primary)
Check the current conversation for signals about what the user has been working on. If an earlier command in this session targeted a specific issue or PR, use that as the comment target.
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.
- 2d ago First seen · 132 lines · 15 tokens per session scan A 75cb3c698543
push is a command published in the GitHub repository LeanAndMean/mach10 (20 stars, last pushed 3mo ago), licensed MIT. It adds 15 tokens to every session and 1,592 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 commands, from other repositories
psm
/oh-my-claudecode:psm is a compatibility alias for /oh-my-claudecode:project-session-manager.
project
Generate project documentation (product.md, structure.md, tech.md, codemaps/).
version
Display current guide and Claude Code versions.
diff-docs
Compare official Anthropic docs baseline vs current snapshot (no network — instant).
release
This compatibility command keeps /oh-my-claudecode:release available without loading the full release skill description in every Claude Code session.
task-verify
PitWay: Run an inprogress task's approved verification command and persist evidence.