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/christopherlouet/claude-baseWrote 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/christopherlouet/claude-base/work-commit-push-pr)<a href="https://agentmods.dev/commands/christopherlouet/claude-base/work-commit-push-pr"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/work-commit-push-pr/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/christopherlouet/claude-base/work-commit-push-pr"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/work-commit-push-pr.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.00363 |
| Opus 5.5 | $0.00000 | $0.00145 |
| Sonnet 5.5 | $0.00000 | $0.00073 |
| Haiku 4.5 | $0.00000 | $0.00036 |
Grade A, and why
work-commit-push-pr 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.
What it actually says
WORK-COMMIT-PUSH-PR Agent
Pointer: Claude Code ships a native /commit-push-pr that owns the commit + push + PR macro. This command adds the foundation's pre-flight gate and convention sources on top — it does not re-implement the macro.
Context
$ARGUMENTS
Workflow
- Pre-flight gate (foundation delta) — before anything ships: run the quality checks
(tests, lint, typecheck), verify not on
main/master, no sensitive files (.env, secrets), no stray debug (console.log). Stop if anything fails. - Delegate the macro to native
/commit-push-pr— it commits, pushes to the configured remote, and opens the PR. Hold it to the foundation's conventions: the commit message follows/work:work-commit(Conventional Commits, atomic), the PR body follows/work:work-pr(title, summary, test plan). - Check CI status after the PR is created.
Expected output
- Verification: quality report (tests, lint, types)
- PR: URL of the created PR with full description
Related agents
| Agent | Usage |
|---|---|
/work:work-commit |
Commit conventions (message, atomicity) — source of record |
/work:work-pr |
PR conventions (description, test plan) — source of record |
/qa:qa-review |
Self-review before PR |
IMPORTANT: Always run the quality gate before the native macro.
NEVER commit on main/master directly, and NEVER include sensitive files (.env, secrets).
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 · 37 lines · 0 tokens per session scan A 1a4d3d71f7ee
work-commit-push-pr is a command published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 363 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-09-03.
Other commands, from other repositories
deploy
Deploy application with pre/post-deploy checks.
watch-ci
Spawn a background Haiku-backed subagent to watch CI for the current branch (or specified target). Provider-agnostic — the subagent inspects project signals to identify the CI system (GitHub Actions, GitLab CI, CircleCI, etc.) and picks the right CLI. Returns immediately; reports back when CI reaches a terminal state.
undo-commit
Soft-undo the last commit. Restores its changes as staged, leaves working tree intact. Refuses if HEAD is already pushed to a tracked remote.
pull-repos
Pull all repos (parent + marketplace clones + configured project repos).
validate-pr-description
Use when validating a PR title and description for conventional commit format, issue linking keywords, and template compliance before submission.
commit
Stage, commit, and optionally ship further. Pass an escalation token (push, pr, merge, squash, squash merge) to skip the prompt. With no token, commits then asks how far to ship. Delegates message format to the atomic-git-discipline skill.