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/runnithan/claudex-setupWrote 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/runnithan/claudex-setup/pr)<a href="https://agentmods.dev/commands/runnithan/claudex-setup/pr"><img src="https://agentmods.dev/badge/commands/runnithan/claudex-setup/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/runnithan/claudex-setup/pr"><img src="https://agentmods.dev/badge/commands/runnithan/claudex-setup/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.00009 | $0.00317 |
| Opus 5.5 | $0.00004 | $0.00127 |
| Sonnet 5.5 | $0.00002 | $0.00063 |
| Haiku 4.5 | $0.00001 | $0.00032 |
Grade A, and why
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
Create a pull request from the current branch:
-
Get branch info: Run
git branch --show-currentto get the current branch name. If it starts with a ticket key (for examplePROJ-12), carry that key into the title. -
Gather changes:
- Run
git log main..HEAD --onelinefor commit history - Run
git diff main...HEAD --statfor changed files summary
- Run
-
Create the PR with the
ghCLI, which takes the owner and repo from the current checkout:gh pr create --base main --head "$(git branch --show-current)" \ --title "<title>" --body "<body>"-
title: Conventional Commit style,{type}: {concise description of changes}(under 70 chars), prefixed with the ticket key if step 1 found one -
body: use this template and keep the whole body shorter than the diff it describes:## Summary: at most 5 one-line bullets, what changed and why## Risk: one line on what could break and how widely## Test plan: a checklist of what was actually run
Leave out anything a reviewer can read from the diff itself.
-
-
Report: Show the PR URL and a summary of what was included.
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 Changed · +7 lines · -4 tokens per session 16bb439e8a8c
- 1mo ago First seen · 23 lines · 13 tokens per session scan A c27edf89b280
pr is a command published in the GitHub repository runnithan/claudex-setup (1 stars, last pushed yesterday), licensed MIT. It adds 9 tokens to every session and 317 once invoked, about $0.0000 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
auto
An automated coding workflow runs a software task from planning through code changes, checks, and a pull request. A pull request is a proposed change for review before it is merged into the main codebase.
sync
A command that pulls the latest code from the main Git branch and updates the project's key planning and instruction documents to match it.
deploy
Deploy application with pre/post-deploy checks.
pull-repos
Pull all repos (parent + marketplace clones + configured project repos).
auto-claude
Invoke Auto-Claude autonomous coding framework for complex feature implementation.
worktree-cleanup
A command for removing a Git worktree, which is a separate working folder linked to the same repository, after its pull request is merged.