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/JansenAnalytics/claudexWrote 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/jansenanalytics/claudex/ship)<a href="https://agentmods.dev/commands/jansenanalytics/claudex/ship"><img src="https://agentmods.dev/badge/commands/jansenanalytics/claudex/ship/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/jansenanalytics/claudex/ship"><img src="https://agentmods.dev/badge/commands/jansenanalytics/claudex/ship.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.00017 | $0.00684 |
| Opus 5.5 | $0.00007 | $0.00274 |
| Sonnet 5.5 | $0.00003 | $0.00137 |
| Haiku 4.5 | $0.00002 | $0.00068 |
Grade A, and why
ship 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
Commit and push the current work safely. Honor the user's git identity (<your-git-email>, GitHub user <your-github-username>). Use ~/.local/bin/gh for any GitHub auth/remote ops. Work through the steps in order; STOP early if a gate fails. Optional commit message: $ARGUMENTS.
- Repo check — run
git rev-parse --show-toplevel. If it errors (not a git repo), report "Not a git repo — nothing to ship" and STOP. - Change check — run
git status --porcelainandgit diff --stat HEAD. If both are empty (clean tree, nothing staged/unstaged), report "Working tree clean — nothing to commit" and STOP. - Secret safety — inspect the changed file list. ABORT (do not stage/commit) and warn if any of these are about to be committed:
- files matching
.env,*.key,*.pem,*.secret,id_rsa*,*credentials* git diff HEADcontent matchingANTHROPIC_API_KEY,OPENAI_API_KEY,sk-,ghp_,github_pat_, or other token-like strings List the offending file(s)/line(s) and STOP. Tell the user to gitignore or unstage them first.
- files matching
- Branch guard — run
git rev-parse --abbrev-ref HEAD. If onmainormaster: do NOT commit straight to it. Derive a short kebab slug from the change and create + switch tofeat/<slug>viagit checkout -b feat/<slug>BEFORE committing. (Exception: a tiny docs-only fix may go to main — but ask the user first; don't assume.) If already on a feature branch, stay on it. - Commit —
git add -A, then commit. Use$ARGUMENTSverbatim as the subject if provided; otherwise generate a conventional-commit subject (feat:/fix:/docs:/chore:) inferred from the diff. End every commit message with a blank line and the trailer:Co-Authored-By: Claude Opus 4.8 <[email protected]>Set author/committer to the user's identity if not already configured. - Push —
git push -u origin HEAD. If no remote exists or push fails on auth, report the exact error and STOP (don't silently retry). - Report — one Telegram-friendly message, bullets only:
- Branch:
<name> - Commit:
<short-sha>— subject line - Files: count + key paths
- Push: ✅ pushed / ❌ failed (with reason)
If the branch warrants a PR (feature branch, non-main target), OFFER: "Want me to open a PR?
gh pr create ..." — do NOT auto-open one. Don't pad. Don't congratulate.
- Branch:
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 · 26 lines · 17 tokens per session scan A fe2a84293cf2
ship is a command published in the GitHub repository JansenAnalytics/claudex (5 stars, last pushed 3mo ago), licensed MIT. It adds 17 tokens to every session and 684 once invoked, about $0.0001 per session on Opus 5.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-31.
Other commands, from other repositories
standup
Review my git commits from the past workday and generate a standup summary.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
git-workflow
Run review, tests, and commit steps, then prepare a pull request.
session-report
Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.
commit
Context-aware Git commit assistant with smart pre-commit checks.