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/jmagar/claude-homelabWrote 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/jmagar/claude-homelab/quick-push)<a href="https://agentmods.dev/commands/jmagar/claude-homelab/quick-push"><img src="https://agentmods.dev/badge/commands/jmagar/claude-homelab/quick-push.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.00015 | $0.01092 |
| Opus 5 | $0.00008 | $0.00546 |
| Sonnet 5 | $0.00003 | $0.00218 |
| Haiku 4.5 | $0.00002 | $0.00109 |
Grade A, and why
quick-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 7d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context
- Current branch: !
git branch --show-current - Git status: !
git status --short - Remote info: !
git remote -v | head -1
Your task
Work through these steps in order:
1. Orient
- Check if we're on a feature branch (not main/master)
- If on main/master, create a new feature branch with a descriptive name based on the changes
- Run
git diff --stat HEADto understand the scope of changes - Run
git log --oneline -5to understand recent commit conventions
2. Bump version (before staging)
Detect the project type and bump the version based on the commit message you'll generate.
Bump rules (based on the commit message prefix you'll draft in step 3):
feat!:orBREAKING CHANGE→ major (X+1.0.0)featorfeat(...)→ minor (X.Y+1.0)- Everything else (
fix,chore,refactor,test,docs, etc.) → patch (X.Y.Z+1)
Process:
- Read the current version from the primary manifest (first match:
Cargo.toml,package.json,pyproject.toml) - Draft the commit message mentally (you'll finalize it in step 4)
- Determine bump type from the commit prefix
- Calculate the new version
- Update the version in ALL of these files that exist in the repo:
Cargo.toml—version = "X.Y.Z"in[package]package.json—"version": "X.Y.Z"pyproject.toml—version = "X.Y.Z"in[project].claude-plugin/plugin.json—"version": "X.Y.Z".codex-plugin/plugin.json—"version": "X.Y.Z"gemini-extension.json—"version": "X.Y.Z"
- If Rust: run
cargo checkto updateCargo.lock(it records the version) - Report:
Version: X.Y.Z → A.B.C (bump type)and list which files were updated
Skip conditions:
- Version is
0.0.0or0.0.1(project not yet versioned) - No manifest file found
- The
--no-bumpflag was passed as a skill argument
3. Update CHANGELOG.md (before staging)
If a CHANGELOG.md exists in the repo root:
- Find the most recently documented commit in the changelog (look for commit hashes in the table)
- Run
git log --oneline <last_documented_sha>..HEADto get undocumented commits - If there are new commits, update the changelog:
- Add new rows to the commit summary table (newest first)
- Update the Highlights section with grouped summaries
- Keep the existing structure and style
- If no CHANGELOG.md exists, skip this step
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.
- 7d ago First seen · 95 lines · 15 tokens per session scan A 862e919b2137
quick-push is a command published in the GitHub repository jmagar/claude-homelab (77 stars, last pushed 1mo ago), licensed MIT. It adds 15 tokens to every session and 1,092 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
new-feature-branch
Branch-from-fresh-main boilerplate — checkout main, pull, create branch with a meaningful name, push empty so it can be protected.
changelog
Generate a structured changelog from recent git commits, categorized by change type.
commit-push-pr
An automated Git workflow that checks a project, synchronizes documentation, commits changes, and can create or merge a GitHub pull request. A pull request is a request for teammates to review and add changes to a shared codebase.
setup-git
/setup-git is per-repo platform secret setup — most importantly SYNCPAT, the fine-grained PAT that allows the issue-sync workflow to author issues as the maintainer instead of as github-actions[bot]. Without SYNCPAT, every synced issue carries authorassociation: NONE and the t2449 worker-briefed auto-merge gate…
quick-commit
A quick Git command for committing and pushing a small code change. Git is the tool that records code versions and sends them to a shared repository.
devkit.github.create-pr
Creates a GitHub pull request with branch creation, commits, and detailed description. Use when you need to submit changes for review.